Closed Bug 49130 Opened 24 years ago Closed 23 years ago

[MLK] JavaPackage_resolve() leaks a C string

Categories

(Core Graveyard :: Java: Live Connect, defect, P4)

defect

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9

People

(Reporter: beard, Assigned: beard)

References

()

Details

(Keywords: memory-leak)

Attachments

(2 files)

If jsj_EnterJava(cx, &jEnv) returns a NULL jEnv, the C string newPath is leaked.
Attached file leak report
Keywords: mlk
This is a very noticeable leak, as it happens whenever a new JS context/global 
object is initialized in the DOM.
Keywords: nsbeta3
Low priority leak, only occurs when Java isn't installed.
Status: NEW → ASSIGNED
Priority: P3 → P4
Whiteboard: [nsbeta3+]
PDT is downgrading to [nsbeta3-], looking for big bloat.  How many javascript 
context would a page have?  Seems like low priority to fix.
Whiteboard: [nsbeta3+] → [nsbeta3-][minus]
asking for reconsideration. java isn't installed in some of our embedding cases.
Whiteboard: [nsbeta3-][minus] → [minus]
Whiteboard: [minus] → [nsbeta3-] [minus]
Here's a trivial patch to fix. Given the simplicity of this fix, it is very low 
risk and thus I'd nominate for RTM.
Keywords: rtm
Whiteboard: [nsbeta3-] [minus] → [nsbeta3-] [minus] [rtm+]
PDT marking [rtm-] because small leaks with little user impact aren't going to
move the needle on Seamonkey stability. If appropriate, please check in on the
trunk.
Whiteboard: [nsbeta3-] [minus] [rtm+] → [nsbeta3-] [minus] [rtm-]
Moving to 0.9.
Keywords: nsbeta3, rtm
Whiteboard: [nsbeta3-] [minus] [rtm-]
Target Milestone: --- → mozilla0.9
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Marking Verified - 
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: