Closed Bug 339721 Opened 18 years ago Closed 14 years ago

gc_dump_thing doesn't handle null JSXMLNamespace::prefix

Categories

(Core :: JavaScript Engine, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: dbaron, Assigned: dbaron)

References

Details

(Whiteboard: [patch])

Attachments

(1 file)

gc_dump_thing's code for the GCX_NAMESPACE case doesn't handle ns->prefix being null, which appears (from other code I've looked at that sets prefix to null) to be valid. I hit this running GC_MARK_DEBUG, with js_DumpGCHeap set, starting Mozilla. ns->uri in the case with null ns->prefix was "http://www.mozilla.org/microsummaries/0.1".
Attached patch patch (deleted) — Splinter Review
Attachment #223822 - Flags: review?(brendan)
Status: NEW → ASSIGNED
Whiteboard: [patch]
Comment on attachment 223822 [details] [diff] [review] patch Sure, sorry I missed this for so long. /be
Attachment #223822 - Flags: review?(brendan) → review+
These bugs are all part of a search I made for js bugs that are getting lost in transit: http://tinyurl.com/jsDeadEndBugs They all have a review+'ed, non-obsoleted patch and are not marked fixed-in-tracemonkey or checkin-needed but have not seen any activity in 300 days. Some of these got lost simply because the assignee/patch provider never requested a checkin, or just because they were forgotten about.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Depends on: 366725
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: