Ehsan Akhgari
6b77452659
Bug 758992 - Make the classes which use the XPCOM nsISupports implementation macros final, to avoid the warning about deleting using a pointer to a base class with virtual functions and no virtual dtor (XPCOM parts); r=bsmedberg
2012-06-05 19:51:58 -04:00
Gervase Markham
e95524780d
Bug 716478 - update licence to MPL 2.
2012-05-21 12:12:37 +01:00
Michael Wu
ac54b41b01
Bug 675553 - Switch from PRBool to bool on a CLOSED TREE , r=bsmedberg,khuey,bz,cjones
...
--HG--
rename : tools/trace-malloc/bloatblame.c => tools/trace-malloc/bloatblame.cpp
2011-09-28 23:19:26 -07:00
Boris Zbarsky
f04def28fa
Bug 650379. Add a new XPCOM timer type that is like TYPE_REPEATING_PRECISE but does not swamp the event queue if the callback takes longer than the timer interval to run. r=cjones, sr=brendan
...
This implements proposal 3 from bug 650379 comment 13. The main difference
between TYPE_REPEATING_PRECISE and TYPE_REPEATING_PRECISE_CAN_SKIP is to not
AddTimer the REPEATING_PRECISE_CAN_SKIP timer until after the callback has run;
this guarantees that no more timer events will be posted until after the
callback finishes executing. A secondary change is to make
REPEATING_PRECISE_CAN_SKIP timers advance their firing time to mDelay from when
PostTimerEvent is called, not mDelay from the old mTimeout. While this arguably
makes them less precise, the alternative is that if a timer is significantly
delayed for some reason (e.g. because the user puts the computer to sleep for a
while) it will then fire a whole bunch of times to "catch up" to where it's
supposed to be, advancing its firing time by mDelay at a time. That seems
undesirable.
An alternate approach would have been to readd the timer from inside
PostTimerEvent, but only if we're not in the middle of firing the timer. That
would allow more precise timers in the case when the callback is not taking too
long, but still handle gracefully the case when the callback is
slow. Unfortunately this falls down if something _else_ is hogging the main
thread event loop (e.g. some other timer has a slow callback, or whatever); in
that case we would post multiple events for the one precise timer while the
event-loop-hogging operation is running. So I don't think we should do that.
2011-04-28 19:33:52 -04:00
Boris Zbarsky
1051536d0b
Bug 558306 part 2. Switch XPCOM timers to TimeDuration/TimeStamp. r=cjones, sr=brendan
2010-07-15 09:59:24 -04:00
Boris Zbarsky
1d79cd4137
Backing out rev b567a93a5086 (bug 558306) to fix test orange
2010-07-15 13:49:28 -04:00
Boris Zbarsky
4c09b4504c
Bug 558306 part 2. Switch XPCOM timers to TimeDuration/TimeStamp. r=cjones, sr=brendan
2010-07-15 09:59:24 -04:00
Ben Turner
6008210f62
Bug 443877 - "Need a way to point timers at a different event target". r=bsmedberg.
2008-07-24 10:20:33 -07:00
jwalden@mit.edu
afab03375a
Bug 420521 - Leaking nsThread and nsTimerImpl running full set of Mochitests. This fixes the last refcounted leak on OS X Mochitests! Zounds! r=brendan, sr=dbaron, a=blocker
2008-03-10 14:05:46 -07:00
vladimir@pobox.com
54f560d6d3
b=417115, animated image causes recursion during shutdown ; r=stuart
2008-02-13 22:51:06 -08:00
sayrer@gmail.com
0a445b1337
Bug 401137. Silence ASSERTION: RefreshURIList timer callbacks should only be RefreshTimer objects. Docshell expects to be able to getCallback during a Timer fire. r=bzbarsky, sr=brendan, a=mconnor
2007-10-30 08:56:59 -07:00
sayrer@gmail.com
10e9f3825a
Bug 330128. Calling cancel() on a timer doesn't drop ref to the callback. r=brendan, sr=bzbarsky, a=beltzner
2007-10-24 12:11:41 -07:00
roc+@cs.cmu.edu
0054412272
Bug 374866. Reftests for text-transform. r=dbaron
2007-03-22 16:01:14 -07:00
jwalden%mit.edu
0fa98d8e8e
Bug 420521 - Leaking nsThread and nsTimerImpl running full set of Mochitests. This fixes the last refcounted leak on OS X Mochitests! Zounds! r=brendan, sr=dbaron, a=blocker
2008-03-10 21:05:46 +00:00
vladimir%pobox.com
d7d4dee380
b=417115, animated image causes recursion during shutdown ; r=stuart
2008-02-14 06:51:06 +00:00
sayrer%gmail.com
e0c8f72abe
Bug 401137. Silence ASSERTION: RefreshURIList timer callbacks should only be RefreshTimer objects. Docshell expects to be able to getCallback during a Timer fire. r=bzbarsky, sr=brendan, a=mconnor
2007-10-30 15:57:00 +00:00
sayrer%gmail.com
e3c15edea9
Bug 330128. Calling cancel() on a timer doesn't drop ref to the callback. r=brendan, sr=bzbarsky, a=beltzner
2007-10-24 19:11:41 +00:00
darin%meer.net
d96f34ca2f
fixes bug 333167 "remove idle timer / timer manager after bug 326273 is fixed" r=pavlov
2006-06-29 00:01:58 +00:00
darin%meer.net
7d3e7d7acd
landing patch for bug 326273 "Implement nsIThreadManager" (Mac portions by Mark Mentovai) with reviews from bienvenu, bsmedberg, bzbarsky, josh, roc, and ssieb
2006-05-10 17:30:15 +00:00
bsmedberg%covad.net
5f4c45344b
Allow XPCOM to be restarted. r+sr=darin with grudging consent from dougt. Bug 239819
2004-05-11 09:38:50 +00:00
gerv%gerv.net
6f486a3c92
Bug 236613: change to MPL/LGPL/GPL tri-license.
2004-04-18 14:21:17 +00:00
bryner%brianryner.com
bc829daafa
Bug 229875 - eliminate unnecssary public/virtual destructors. This patch changes all refcounted classes under xpcom/, which aren't inherited from or used on the stack, to have private, nonvirtual destructors. r=dougt, sr=dbaron.
2004-01-15 06:14:18 +00:00
brendan%mozilla.org
1c7790b52a
Fix Timer re-init to drop any old references (215163, sr=dbaron, r?pavlov).
2003-08-06 00:37:43 +00:00
brendan%mozilla.org
abcf2b2365
Implement support for re-initializing timers (even one-shots), and doc-comment
...
on how timers may be canceled, re-initialized, and canceled-then-re-initialized
in nsITimer.idl (181961, r=pavlov, sr=alecf). This helps client code conserve
instances, saving on cycles and malloc/component-manager froth.
2002-12-04 00:57:20 +00:00
dougt%netscape.com
d94b37c68a
Fixes up the timer interface. b157136, r=rpotts@netscape.com, sr=alecf@netscape.com, a=rjesup@wgate.com
2002-09-07 05:38:16 +00:00
dougt%netscape.com
747cfeb781
Attempting to fix the idle time topcrash. b=155447, r=pavlov, sr=dveditz
2002-08-09 04:03:45 +00:00
cbiesinger%web.de
6197948cc3
bug 115473 r=pavlov sr=brendan
...
Remove timer priorities
2002-06-11 20:47:04 +00:00
pavlov%netscape.com
e8165f5bb3
fixing bug 142113. r=varga sr=brendan
2002-05-15 10:28:42 +00:00
brendan%mozilla.org
ca47762b00
Followup fix for 138791, neil@parkwaycc.co.uk's superior bit-fu (r=rjesup, sr=waterson, a=asa).
2002-05-01 23:34:18 +00:00
brendan%mozilla.org
df25211e6f
Handle wraparound of PRIntervalTime, plus crucial fixes thanks to Ere Maijala <ere@atp.fi> (138791, r=rjesup, sr=waterson).
2002-04-25 21:07:54 +00:00
dbaron%fas.harvard.edu
5edc868516
Relanding pavlov's changes for bug 129953, in pieces.
2002-04-14 00:27:16 +00:00
brade%netscape.com
ee14174c18
backout changes by pavlov (bug 136677) r=cathleen
2002-04-11 18:50:42 +00:00
pavlov%netscape.com
3a549502ef
re-landing 129953
2002-04-11 07:55:53 +00:00
pavlov%netscape.com
180ada0b21
backing out changes for 129953...
2002-04-11 05:38:55 +00:00
pavlov%netscape.com
781ff3a1ca
bug 129953 r=rjesup sr=rpotts
2002-04-10 04:41:23 +00:00
brendan%mozilla.org
c50bca002a
Try to fix design flaw where a timer's destructor races with TimerThread::Run -- really want a better design, but this patches the problem in the context of the current design (118004, r=dbradley/pavlov, sr=shaver/jband, a=asa).
2002-03-08 20:11:49 +00:00
sgehani%netscape.com
236293ae2b
Land update notifications.
...
b=120201; r=law,pavlov; sr=dveditz
2002-02-20 04:01:34 +00:00
brendan%mozilla.org
81ddd6526f
Digital filter for adaptive timeout adjustment, needs trunk baking, makes things better so far (117061, r=pavlov, sr=jst).
2002-02-18 00:10:55 +00:00
pavlov%netscape.com
cec4deba1a
fixing tomorrow's blocker today (115527). r=ben sr=mscott
2001-12-17 06:59:55 +00:00
pavlov%netscape.com
5cd1b8e131
bug 78611. New XP threadsafe timer implementation. r=dougt sr=brendan
2001-12-16 06:13:17 +00:00