Skip to content
Snippets Groups Projects
  1. Dec 20, 2020
  2. Dec 17, 2020
  3. Nov 10, 2020
  4. Oct 15, 2020
  5. Oct 10, 2020
  6. Oct 05, 2020
  7. Sep 28, 2020
  8. Sep 26, 2020
  9. Sep 11, 2020
  10. Aug 24, 2020
  11. Aug 21, 2020
  12. Aug 18, 2020
  13. Jul 04, 2020
  14. Jun 30, 2020
  15. Apr 20, 2020
  16. Apr 13, 2020
  17. Mar 25, 2020
    • Nat Goodspeed's avatar
      DRTVWR-494: Defend LLInstanceTracker against multi-thread usage. · 9d5b8976
      Nat Goodspeed authored
      The previous implementation went to some effort to crash if anyone attempted
      to create or destroy an LLInstanceTracker subclass instance during traversal.
      That restriction is manageable within a single thread, but becomes unworkable
      if it's possible that a given subclass might be used on more than one thread.
      
      Remove LLInstanceTracker::instance_iter, beginInstances(), endInstances(),
      also key_iter, beginKeys() and endKeys(). Instead, introduce key_snapshot()
      and instance_snapshot(), the only means of iterating over LLInstanceTracker
      instances. (These are intended to resemble functions, but in fact the current
      implementation simply presents the classes.) Iterating over a captured
      snapshot defends against container modifications during traversal. The term
      'snapshot' reminds the coder that a new instance created during traversal will
      not be considered. To defend against instance deletion during traversal, a
      snapshot stores std::weak_ptrs which it lazily dereferences, skipping on the
      fly any that have expired.
      
      Dereferencing instance_snapshot::iterator gets you a reference rather than a
      pointer. Because some use cases want to delete all existing instances, add an
      instance_snapshot::deleteAll() method that extracts the pointer. Those cases
      used to require explicitly copying instance pointers into a separate
      container; instance_snapshot() now takes care of that. It remains the caller's
      responsibility to ensure that all instances of that LLInstanceTracker subclass
      were allocated on the heap.
      
      Replace unkeyed static LLInstanceTracker::getInstance(T*) -- which returned
      nullptr if that instance had been destroyed -- with new getWeak() method
      returning std::weak_ptr<T>. Caller must detect expiration of that weak_ptr.
      
      Adjust tests accordingly.
      
      Use of std::weak_ptr to detect expired instances requires engaging
      std::shared_ptr in the constructor. We now store shared_ptrs in the static
      containers (std::map for keyed, std::set for unkeyed).
      
      Make LLInstanceTrackerBase a template parameterized on the type of the static
      data it manages. For that reason, hoist static data class declarations out of
      the class definitions to an LLInstanceTrackerStuff namespace.
      
      Remove the static atomic sIterationNestDepth and its methods incrementDepth(),
      decrementDepth() and getDepth(), since they were used only to forbid creation
      and destruction during traversal.
      
      Add a std::mutex to static data. Introduce an internal LockStatic class that
      locks the mutex while providing a pointer to static data, making that the only
      way to access the static data.
      
      The LLINSTANCETRACKER_DTOR_NOEXCEPT macro goes away because we no longer
      expect ~LLInstanceTracker() to throw an exception in test programs.
      That affects LLTrace::StatBase as well as LLInstanceTracker itself.
      
      Adapt consumers to the new LLInstanceTracker API.
      9d5b8976
  18. Mar 24, 2020
  19. Mar 19, 2020
  20. Sep 19, 2019
  21. Aug 05, 2019
  22. Dec 14, 2018
    • Nat Goodspeed's avatar
      SL-10153: Review and rationalize fetching paths from environment. · c4096f67
      Nat Goodspeed authored
      Use LLStringUtil::getenv() or getoptenv() whenever we fetch a string that will
      be used as a pathname.
      
      Use LLFile::tmpdir() instead of getenv("TEMP").
      
      As an added extra-special bonus, finally clean up $TMP/llcontrol-test-zzzzzz
      directories that have been accumulating every time we run a local build!
      c4096f67
  23. Nov 19, 2018
  24. Sep 07, 2018
  25. Sep 05, 2018
  26. Jan 24, 2017
    • ruslantproductengine's avatar
      MAINT-6645 - Improvement - Agents that render as jelly dolls should have their... · 6770c273
      ruslantproductengine authored
      MAINT-6645 - Improvement - Agents that render as jelly dolls should have their attachments render at 0 LoD to prevent loading higher LoD complexity in memory thus deterring crashes.
      Comments:
      - Fix based on "RenderAutoMuteByteLimit" setting.
      - File indra/llxml/llcontrol.h - add all signals to 0 group.
        It garanty that handlers (in indra/newview/llviewercontrol.cpp) will be called last.
      6770c273
  27. Dec 04, 2016
  28. Nov 27, 2016
  29. Mar 23, 2016
  30. Nov 10, 2015
  31. Apr 29, 2015
  32. Apr 17, 2015
  33. Apr 16, 2015
Loading