Closed Bug 637915 Opened 14 years ago Closed 14 years ago

nsJNIString is leaky with zero length strings.

Categories

(Core Graveyard :: Widget: Android, defect)

x86_64
Android
defect
Not set
normal

Tracking

(fennec2.0+)

RESOLVED FIXED
Tracking Status
fennec 2.0+ ---

People

(Reporter: dougt, Assigned: dougt)

References

Details

Attachments

(1 file)

Attached patch v.1Splinter Review
nsJNIString is leaky with zero length strings.
Attachment #516070 - Attachment is patch: true
Attachment #516070 - Attachment mime type: application/octet-stream → text/plain
Attachment #516070 - Flags: review?(mwu)
dup blocked. this blocks.
tracking-fennec: --- → 2.0+
Comment on attachment 516070 [details] [diff] [review] v.1 Awesome. Just one nit. >+ if (len <= 0) { >+ SetIsVoid(PR_TRUE); >+ } >+ else { >+ Assign(jCharPtr, len); >+ } The style in this file is to have else on the same line as the }.
Attachment #516070 - Flags: review?(mwu) → review+
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Yay! Should I dupe bug 629604 against this then? I think there's still some value to dropping the nsJNIString type and just using a helper function to properly stuff the bits into an nsString.
Assignee: nobody → doug.turner
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: