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)
Core Graveyard
Java: Live Connect
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9
People
(Reporter: beard, Assigned: beard)
References
()
Details
(Keywords: memory-leak)
Attachments
(2 files)
4.75 KB,
text/html
|
Details | |
616 bytes,
patch
|
Details | Diff | Splinter Review |
If jsj_EnterJava(cx, &jEnv) returns a NULL jEnv, the C string newPath is leaked.
Assignee | ||
Comment 1•24 years ago
|
||
Assignee | ||
Comment 2•24 years ago
|
||
This is a very noticeable leak, as it happens whenever a new JS context/global object is initialized in the DOM.
Keywords: nsbeta3
Assignee | ||
Comment 3•24 years ago
|
||
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]
Comment 5•24 years ago
|
||
asking for reconsideration. java isn't installed in some of our embedding cases.
Whiteboard: [nsbeta3-][minus] → [minus]
Assignee | ||
Updated•24 years ago
|
Whiteboard: [minus] → [nsbeta3-] [minus]
Assignee | ||
Comment 6•24 years ago
|
||
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+]
Assignee | ||
Comment 7•24 years ago
|
||
Comment 8•24 years ago
|
||
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-]
Assignee | ||
Comment 9•23 years ago
|
||
Moving to 0.9.
Assignee | ||
Comment 10•23 years ago
|
||
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•