Fix the documentation of TimerEventAllocator threading expectations, no bug, DONTBUILD
authorEhsan Akhgari <ehsan@mozilla.com>
Mon, 18 Feb 2013 21:13:26 -0500
changeset 132167 fe5e2415c67c25782e4deb71165f16d3fdd02ae4
parent 132166 0169230798315264391d7c667e33a868abc79d29
child 132168 c36791017011317b5471bd63d6c818a69f2fcdcf
push id2323
push userbbajaj@mozilla.com
push dateMon, 01 Apr 2013 19:47:02 +0000
treeherdermozilla-beta@7712be144d91 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
milestone21.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Fix the documentation of TimerEventAllocator threading expectations, no bug, DONTBUILD
xpcom/threads/nsTimerImpl.cpp
--- a/xpcom/threads/nsTimerImpl.cpp
+++ b/xpcom/threads/nsTimerImpl.cpp
@@ -56,17 +56,17 @@ myNS_MeanAndStdDev(double n, double sumO
 #endif
 
 namespace {
 
 // TimerEventAllocator is a fixed size allocator class which is used in order
 // to avoid the default allocator lock contention when firing timer events.
 // It is a thread-safe wrapper around nsFixedSizeAllocator.  The thread-safety
 // is required because nsTimerEvent objects are allocated on the timer thread,
-// and freed on the main thread.  Since this is a TimerEventAllocator specific
+// and freed on another thread.  Since this is a TimerEventAllocator specific
 // lock, the lock contention issue is only limited to the allocation and
 // deallocation of nsTimerEvent objects.
 class TimerEventAllocator : public nsFixedSizeAllocator {
 public:
     TimerEventAllocator() :
       mMonitor("TimerEventAllocator")
   {
   }