Closed
Bug 3653
Opened 26 years ago
Closed 26 years ago
MLK: nsCaret leaks in reflow.
Categories
(Core :: DOM: Selection, defect, P1)
Core
DOM: Selection
Tracking
()
VERIFIED
FIXED
M3
People
(Reporter: bruce, Assigned: ramiro)
Details
Leaks on every reflow it seems. Every build that I've done from March 8 - 11,
1999 at least.
MLK: 96 bytes leaked in 3 blocks
* This memory was allocated from:
malloc [rtlib.o]
__bUiLtIn_nEw [libgcc.a]
__builtin_new [rtlib.o]
NS_NewTimer(nsITimer**) [nsTimer.cpp:176]
nsCaret::PrimeTimer() [nsCaret.cpp:211]
nsCaret::StartBlinking() [nsCaret.cpp:226]
nsCaret::SetCaretVisible(int) [nsCaret.cpp:139]
PresShell::EnableCaret() [nsPresShell.cpp:1007]
PresShell::ResizeReflow(int,int) [nsPresShell.cpp:934]
PresShell::ResizeReflow(nsIView*,int,int) [nsPresShell.cpp:1972]
nsViewManager::SetWindowDimensions(int,int) [nsViewManager.cpp:354]
nsViewManager::DispatchEvent(nsGUIEvent*,nsEventStatus&)
[nsViewManager.cpp:1571]
HandleEvent(nsGUIEvent*) [nsView.cpp:63]
nsWidget::DispatchEvent(nsGUIEvent*,nsEventStatus&) [nsWidget.cpp:815]
nsWidget::DispatchWindowEvent(nsGUIEvent*) [nsWidget.cpp:775]
nsWidget::OnResize(nsRect&) [nsWidget.cpp:249]
idle_resize_cb(void*) [nsGtkEventHandler.cpp:412]
g_idle_dispatch [gmain.c:1228]
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 (3 times); last block at 0x650ba8
Comment 1•26 years ago
|
||
This may be a bug in the GTK timer implementation.
Updated•26 years ago
|
Assignee: sfraser → ramiro
Comment 2•26 years ago
|
||
This is a GTK leak. Reassigning for closure.
Updated•26 years ago
|
Assignee: ramiro → sfraser
Updated•26 years ago
|
Target Milestone: M3
Comment 3•26 years ago
|
||
Changed to M3
Updated•26 years ago
|
Assignee: sfraser → ramiro
Comment 4•26 years ago
|
||
Ramiro should own this. It's fixed already, I think (was a GTK timer bug).
Comment 5•26 years ago
|
||
ramiro, can you mark it fixed?
Status: NEW → RESOLVED
Closed: 26 years ago
Priority: P3 → P1
Resolution: --- → FIXED
claudius, this should be marked Verified with today's build if all looks well.
Reporter | ||
Comment 7•26 years ago
|
||
ramiro _has_ the fix. it isn't checked in yet.
Comment 9•26 years ago
|
||
Changing a few bugs at once...This is a bug that I have determined I am unable to properly verify. More than likely this would be
because it is outside my expertise or experience, or i don't have the necessary tools.
I am now ASKING PLEASE, please could the bug owner or reporter take it upon themselves to verify the fix for this bug and mark it
VERIFIED? Don't be shy, step right up. Thank you.
Reporter | ||
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Comment 10•25 years ago
|
||
Per a request from Selection and Search component eng (mjudge) and qa (elig),
moving all "Selection and Search" bugs to new "Selection" component. Original
"Selection and Search" component will be retired.
You need to log in
before you can comment on or make changes to this bug.
Description
•