Closed
Bug 3566
Opened 26 years ago
Closed 26 years ago
MLK: Timers leaking
Categories
(Core :: Networking, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: bruce, Assigned: ramiro)
Details
I just started apprunner up and left it sit a while and had this massive leak.
Pull from shortly after Waterson's landing on the evening (PST) of March 9,
1999. Solaris 2.6, gcc 2.7.2.3, purify.
MLK: 254240 bytes leaked in 7945 blocks
* This memory was allocated from:
malloc [rtlib.o]
__bUiLtIn_nEw [libgcc.a]
__builtin_new [rtlib.o]
NS_NewTimer(nsITimer**) [nsTimer.cpp:176]
nsNetlibService::SchedulePollingTimer() [nsNetService.cpp:1192]
nsNetlibService::NetPollSocketsCallback(nsITimer*,void*)
[nsNetService.cpp:1222]
TimerImpl::FireTimeout() [nsTimer.cpp:73]
nsTimerExpired [nsTimer.cpp:188]
g_timeout_dispatch [gmain.c:1147]
g_main_dispatch [gmain.c:647]
g_main_iterate [gmain.c:854]
g_main_run [gmain.c:912]
gtk_main [gtkmain.c:475]
nsAppShell::Run() [nsAppShell.cpp:152]
nsAppShellService::Run() [nsAppShellService.cpp:154]
main [nsAppRunner.cpp:286]
_start [crt1.o]
* Block of 32 bytes (7945 times); last block at 0x8b87f0
Reporter | ||
Updated•26 years ago
|
Assignee: gagan → ramiro
Reporter | ||
Comment 1•26 years ago
|
||
ramiro has a patch for this that clears it all up very nicely. It was a GTK
specific problem.
Assignee | ||
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Changing all Networking Library/Browser bugs to Networking-Core component for
Browser.
Occasionally, Bugzilla will burp and cause Verified bugs to reopen when I do
this in a bulk change. If this happens, I will fix. ;-)
Bulk move of all Networking-Core (to be deleted component) bugs to new
Networking component.
You need to log in
before you can comment on or make changes to this bug.
Description
•