Closed
Bug 616056
Opened 14 years ago
Closed 14 years ago
Registering binary components through manifest multiple times leads to a crash
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
People
(Reporter: WeirdAl, Assigned: benjamin)
References
Details
(Keywords: crash, testcase)
Attachments
(2 files, 1 obsolete file)
|
(deleted),
patch
|
Details | Diff | Splinter Review | |
|
(deleted),
patch
|
mossop
:
review+
|
Details | Diff | Splinter Review |
See attachment 494592 [details] and bug 612088 comment 19. On each pass through Components.manager.autoRegister, the internal module data became progressively worse, until on the fourth pass it crashed with an uninitialized module and an uninitialized local file.
|
Reporter | |
Comment 1•14 years ago
|
||
|
|
Reporter | |
Updated•14 years ago
|
|
|
Reporter | |
Comment 2•14 years ago
|
||
whoops, the testcase had local file paths.
|
|
Reporter | |
Comment 3•14 years ago
|
||
fixed issues with patch - it now shows the bug with Fedora 14 as well.
Attachment #494621 -
Attachment is obsolete: true
|
|
Reporter | |
Updated•14 years ago
|
OS: Windows 7 → All
Hardware: x86 → All
|
Assignee | |
Updated•14 years ago
|
|
|
Assignee | |
Comment 4•14 years ago
|
||
Attachment #494735 -
Flags: review?(dtownsend)
Marking as blocking for beta 8 (see https://bugzilla.mozilla.org/show_bug.cgi?id=612088#c21).
blocking2.0: - → beta8+
|
||
Updated•14 years ago
|
Attachment #494735 -
Flags: review?(dtownsend) → review+
|
||
Comment 7•14 years ago
|
||
Given http://hg.mozilla.org/mozilla-central/rev/96d450e8f445 , can this be marked fixed now?
|
|
Assignee | |
Comment 8•14 years ago
|
||
Yep.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•