MLK: 40 bytes leaked- nsRegionGTK from nsViewManager

VERIFIED FIXED in M13

Status

()

Core
XUL
P1
critical
VERIFIED FIXED
19 years ago
18 years ago

People

(Reporter: Bruce Mitchener, Assigned: Stuart Parmenter)

Tracking

Trunk
Sun
Solaris
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: checked in fix i think. waiting for bruce to verify)

(Reporter)

Description

19 years ago
Pull, build from March 24, 1999. Solaris 2.6, gcc 2.7.2.3, GTK 1.2.0, etc.

MLK: 40 bytes leaked in 2 blocks
  * This memory was allocated from:
        malloc         [rtlib.o]
        XCreateRegion  [Region.c]
        gdk_region_new [gdkregion.c:42]
        nsRegionGTK::Init() [nsRegionGTK.cpp:49]
        nsViewManager::Init(nsIDeviceContext*) [nsViewManager.cpp:261]
        DocumentViewerImpl::MakeWindow(void*,const nsRect&,nsScrollPreference) [
nsDocumentViewer.cpp:622]
        DocumentViewerImpl::Init(void*,nsIDeviceContext*,nsIPref*,const nsRect&,
nsScrollPreference) [nsDocumentViewer.cpp:330]
        nsWebShell::Embed(nsIContentViewer*,const char*,nsISupports*) [nsWebShel
l.cpp:681]

Updated

19 years ago
Target Milestone: M6

Comment 1

19 years ago
marking assigned

Comment 2

19 years ago
moving non-functionality bugs to M7

Comment 3

19 years ago
Marking M8.  If you plan to fix any of these for m7, mark them so.

Comment 4

19 years ago
Moving all Widget Set bugs, past and present, to new HTML Form Controls
component per request from karnaze.  Widget Set component will be retired
shortly.

Comment 5

19 years ago
moving to XP Toolkit/Widgets since these are not HTML form controls
(Assignee)

Comment 6

19 years ago
i can change bugs with bugzilla now. what fun
(Assignee)

Comment 7

19 years ago
s/bugzilla/apprunner/ on my last change ;)
(Reporter)

Comment 8

19 years ago
Yay.  This is now 4 Regions leaking.  Looks to be XP as I saw the same thing
happening in the Xlib code.
(Assignee)

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
(Assignee)

Comment 9

19 years ago
checked in fix
(Assignee)

Updated

19 years ago
Status: RESOLVED → REOPENED
(Assignee)

Comment 10

19 years ago
i don't think this was really fixed.  reopening until someone can verify my last
checkin which should have really fixed it.
(Assignee)

Updated

19 years ago
Status: REOPENED → ASSIGNED
Whiteboard: Checked in potential fix. Waiting for bruce to verify to mark fixed
(Assignee)

Updated

19 years ago
Resolution: FIXED → ---
(Reporter)

Updated

19 years ago
Severity: normal → critical
(Reporter)

Comment 11

19 years ago
I'm still seeing these leak out of control with a build from September 13, 1999.
(Reporter)

Updated

19 years ago
Whiteboard: Checked in potential fix. Waiting for bruce to verify to mark fixed
(Reporter)

Comment 12

19 years ago
clearing status whiteboard. leak still exists.
(Assignee)

Updated

19 years ago
Priority: P3 → P1
Whiteboard: checked in fix i think. waiting for bruce to verify
(Assignee)

Comment 13

19 years ago
checked in fix i think.  waiting for bruce to verify
(Reporter)

Comment 14

19 years ago
This is partially fixed.  We don't leak every region now, but we still leak
some.

Updated

19 years ago
Summary: MLK: nsRegionGTK from nsViewManager → MLK: 40 bytes leaked- nsRegionGTK from nsViewManager

Comment 15

19 years ago
mass migration to m11

Updated

19 years ago
Blocks: 14516
(Assignee)

Updated

19 years ago
Target Milestone: M11 → M12
(Assignee)

Comment 16

19 years ago
beard?  didn't you possibly fix this?  or did i? hmmm.. moving to M12

Comment 17

19 years ago
mass-moving all m12 bugs to m13

Comment 18

18 years ago
giving me rest of phillips open qa contact bugs, sorry for spam

Comment 19

18 years ago
I just tested starting up viewer, and (according to the refcount logger) no
nsRegionGTK objects were leaked.  If there's other steps required to see the
leak, let me know... otherwise I'd say this bug is fixed.
(Assignee)

Updated

18 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago18 years ago
Resolution: --- → FIXED
(Assignee)

Comment 20

18 years ago
agreed

Updated

18 years ago
Status: RESOLVED → VERIFIED

Comment 21

18 years ago
okay, marking verified
You need to log in before you can comment on or make changes to this bug.