Open
Bug 210945
Opened 23 years ago
Updated 3 years ago
[mlk] render view stack not freed up
Categories
(Core :: Web Painting, defect)
Tracking
()
NEW
People
(Reporter: cathleennscp, Unassigned)
Details
(Keywords: memory-leak)
stack not freed. data from trace-malloc build. loading cowtool/Tp test.
operator new(unsigned)
operator new[](unsigned)
RgnRectMemoryAllocator::Alloc()
nsRegion::SetToElements(unsigned)
nsRegion::Copy(nsRegion const&)
nsRegion::SubRect(nsRectFast const&, nsRegion&, nsRegion&) const
nsRegion::SubRegion(nsRegion const&, nsRegion&) const
nsRegion::Sub(nsRegion const&, nsRegion const&)
nsViewManager::OptimizeDisplayList(nsAutoVoidArray*, nsRegion const&, nsRect&,
nsRegion&)
nsViewManager::RenderViews(nsView*, nsIRenderingContext&, nsRegion const&, int)
nsViewManager::Refresh(nsView*, nsIRenderingContext*, nsIRegion*, unsigned)
nsViewManager::DispatchEvent(nsGUIEvent*, nsEventStatus*)
/home/cathleen/spacetrace/opt/mozilla/dist/bin/components/libgklayout.so
nsCommonWidget::DispatchEvent(nsGUIEvent*, nsEventStatus&)
nsWindow::OnExposeEvent(_GtkWidget*, _GdkEventExpose*)
/home/cathleen/spacetrace/opt/mozilla/dist/bin/components/libwidget_gtk2.so
_gtk_marshal_BOOLEAN__BOXED
g_closure_invoke
/usr/lib/libgobject-2.0.so.0
g_signal_emit_valist
gtk_signal_emit
/usr/lib/libgtk-x11-2.0.so.0
gtk_main_do_event
/usr/lib/libgdk-x11-2.0.so.0
gdk_window_process_all_updates
/usr/lib/libgdk-x11-2.0.so.0
/usr/lib/libglib-2.0.so.0
/usr/lib/libglib-2.0.so.0
g_main_context_dispatch
/usr/lib/libglib-2.0.so.0
g_main_loop_run
gtk_main
nsAppShell::Run()
nsAppShellService::Run()
./mozilla-bin
__libc_start_main
I don't see how this can be a leak because the rectangle chunks are supposed to
all be freed by the destructor on the static RegionRectMemoryAllocator. The
static destructor does get called in my Linux build. CCing Dainis who wrote this
code.
Updated•17 years ago
|
QA Contact: ian → layout.view-rendering
Assignee: roc → nobody
| Assignee | ||
Updated•8 years ago
|
Component: Layout: View Rendering → Layout: Web Painting
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•