Closed Bug 268374 Opened 20 years ago Closed 20 years ago

memory leaks in nsScreenGtk :: Init ()

Categories

(Core Graveyard :: GFX: Gtk, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 252143

People

(Reporter: eagle.lu, Assigned: blizzard)

Details

(Keywords: memory-leak)

I use libumem.so and detect a memory leak in nsScreenGtk::Init(). The following
is what I got:
  libumem.so.1`umem_cache_alloc+0x210
                 libumem.so.1`umem_alloc+0x60
                 libumem.so.1`malloc+0x28
                 libglib-2.0.so.0.400.1`g_malloc+0x18
                 libgdk-x11-2.0.so.0.400.9`gdk_property_get+0x298
                 libgfx_gtk.so`void nsScreenGtk::Init+0x120
                 libgfx_gtk.so`unsigned nsScreenManagerGtk::EnsureInit+0x180

                 libgfx_gtk.so`unsigned nsScreenManagerGtk::GetPrimaryScreen+0x3
                4
                 libgfx_gtk.so`unsigned nsDeviceContextGTK::Init+0x1ec
                 libwidget_gtk2.so`void nsBaseWidget::BaseCreate+0x1c4
                 libwidget_gtk2.so`unsigned nsWindow::NativeCreate+0x100
                 libwidget_gtk2.so`unsigned nsWindow::Create+0x70
                 libnsappshell.so`unsigned nsWebShellWindow::Initialize+0x314

                 libnsappshell.so`unsigned nsAppShellService::JustCreateTopWindo
                w+0x338
Severity: normal → critical
Keywords: mlk

*** This bug has been marked as a duplicate of 252143 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.