Closed Bug 4403 Opened 26 years ago Closed 26 years ago

MLK: nsBrowserAppCore::SetEnableCallback() and SetDisableCallback()

Categories

(SeaMonkey :: UI Design, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: bruce, Assigned: rods)

Details

Something changed since March 28, and today, nsBrowserAppCore::SetEnableCallback() seems to be getting called in the startup/shutdown procedure for apprunner. This is causing a small leak it seems. This also happens in nsBrowserAppCore::SetDisableCallback() Build pull from late on March 29, 1999. Solaris 2.6, etc.
This was called by some JavaScript. It might also be related to what seems to be that same Javascript creating an nsBrowserAppCore that also got leaked, but I'm not sure.
Assignee: don → rods
Re-assigned to rods@netscape.com. Rod, this appears to be your code ...
Target Milestone: M5
targeting m5
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
These left over routine and will be removed (I will check this when the tree opens)
Rod -- did you check this? If so, and you did indeed remove the routine, can you please mark as verified? thanks
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.