Skip to content
Snippets Groups Projects
  1. Aug 11, 2021
  2. Jul 15, 2021
  3. Jun 20, 2021
  4. Oct 15, 2020
  5. Aug 17, 2020
  6. Aug 16, 2020
  7. Jul 29, 2020
  8. Apr 13, 2020
  9. Apr 11, 2020
  10. May 16, 2019
  11. Dec 10, 2018
  12. Jun 04, 2018
  13. May 07, 2018
  14. Apr 30, 2018
  15. Jan 24, 2018
  16. Jan 23, 2018
  17. Nov 17, 2017
  18. Nov 16, 2017
    • Nat Goodspeed's avatar
      MAINT-7977: Release the LLRenderTargets when done. · f2ffd637
      Nat Goodspeed authored
      A classic-C array doesn't destroy its individual elements, but a std::vector
      does. Use a std::vector<LLRenderTarget> for dest, so each LLRenderTarget will
      be destroyed. ~LLRenderTarget() calls its release() method.
      f2ffd637
    • Nat Goodspeed's avatar
      MAINT-7977: If getVertexStrider() returns false, abandon benchmark. · dfc07858
      Nat Goodspeed authored
      Ruslan tracked the observed crash to assignments (to create a dummy triangle)
      through an LLStrider<LLVector3> obtained from getVertexStrider(). When
      getVertexStrider() returns false, produce a warning and just skip the rest of
      the benchmark test.
      
      The one bit of explicit cleanup apparently required by that early exit is a
      call to LLImageGL::deleteTextures() to match the preceding generateTextures()
      call. Wrap both in a new TextureHolder class whose destructor takes care of
      cleanup. The only other references to the corresponding U32 array are a couple
      calls to LLTexUnit::bindManual(); add a bind() method to support that.
      
      Also fix apparent bug in the LL_DARWIN special case for "improbably high and
      likely incorrect": the code assigned -1.f (the "couldn't compute" value) to
      gbps, overlooking the fact that gbps is unconditionally recomputed below. In
      the "likely incorrect" stanza, simply return -1.f instead.
      dfc07858
    • ruslantproductengine's avatar
      MAINT-7977 [Alex Ivy] Feature Table crashes · d310159b
      ruslantproductengine authored
      In case of buff->getVertexStrider(v) return false it mean that glMapBufferRange() return NULL
      The next three lines can be the reason of this crash.
      d310159b
  19. Jun 04, 2016
  20. Nov 10, 2015
  21. Dec 10, 2014
  22. Dec 01, 2014
  23. Nov 19, 2014
  24. Nov 18, 2014
  25. Nov 17, 2014
  26. Sep 19, 2014
  27. Mar 24, 2014
  28. Mar 21, 2014
  29. Mar 19, 2014
  30. Dec 06, 2013
Loading