Crash when running Java unit tests that call initXPCOM

RESOLVED FIXED

Status

Core Graveyard
Java to XPCOM Bridge
RESOLVED FIXED
11 years ago
3 years ago

People

(Reporter: jhp (no longer active), Assigned: jhp (no longer active))

Tracking

({verified1.8.1.4})

Other Branch
verified1.8.1.4

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

11 years ago
Created attachment 252386 [details] [diff] [review]
patch

When running any of the Java tests from bug 350886 that call |Mozilla.initXPCOM()|, test crashes when trying to access the directory service provider.

The issue was that I was deleting the provided service provider immediately after calling |NS_InitXPCOM2()| (how did this code ever work?).  Fixed that code to properly use an nsCOMPtr.  Also fixed a related issue in |Mozilla.shutdownXPCOM()|.

Patch attached.
(Assignee)

Comment 1

11 years ago
Checked in to trunk.  -> FIXED
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
(Assignee)

Comment 2

11 years ago
Comment on attachment 252386 [details] [diff] [review]
patch

Asking for 1.8.1.3 approval.  Fix for crasher.  XULRunner only.
Attachment #252386 - Flags: approval1.8.1.3?
Comment on attachment 252386 [details] [diff] [review]
patch

approved for 1.8.1.4, a=dveditz for release-drivers
Attachment #252386 - Flags: approval1.8.1.4? → approval1.8.1.4+
(Assignee)

Comment 4

10 years ago
Checked in to MOZILLA_1_8_BRANCH.
Keywords: fixed1.8.1.4

Updated

10 years ago
Duplicate of this bug: 363510

Comment 6

10 years ago
Javier:  If you have verified this fix with the latest 2.0.0.4 rc builds, can you update the keywords with "verified1.8.14"?  Thanks!
(Assignee)

Updated

10 years ago
Keywords: fixed1.8.1.4 → verified1.8.1.4
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.