Closed Bug 1076977 Opened 11 years ago Closed 11 years ago

Crash reporter doesn't come up anymore an MacOSX

Categories

(Toolkit :: Crash Reporting, defect)

All
macOS
defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla35
Tracking Status
firefox34 --- verified
firefox35 --- verified

People

(Reporter: martijn.martijn, Assigned: spohl)

References

()

Details

(Keywords: regression)

Attachments

(1 file)

I noticed that when the browser crashes, the crash reporter doesn't come up anymore. Str: - Go to https://bugzilla.mozilla.org/attachment.cgi?id=8408204 (testcase from bug 997709) - Print the testcase, or go to Preview Expected result (until bug 997709 gets fixed): - Crash and crash reporter appearing Actual result: - Crash and no crash reporter appearing Syd, could this have anything to do with the Mac v2 codesigning application layout change.
Build Machine bld-lion-r5-003 Source Built from https://hg.mozilla.org/mozilla-central/rev/2399d1ae89e9 Build platform target x86_64-apple-darwin11.2.0
Keywords: regression
I can reproduce this as well. Almost certainly fallout from the v2 bundle changes. Simpler STR: 1) Run Firefox 2) kill -ABRT <firefox pid>
Blocks: 1050944
This may or may not be a duplicate of bug 1075691. The fix for bug 1075691 just landed on inbound. Martijn, would you be able to verify once the inbound build finished compiling? The cset is https://hg.mozilla.org/integration/mozilla-inbound/rev/cabd17a5837a and I'll be happy to post the URL for the build once it becomes available, if necessary.
Flags: needinfo?(martijn.martijn)
Hmm, a quick test with a local debug build with the patch from bug 1075691 applied didn't seem to work either. Should debug builds trigger the crash reporter as well, or only optimized builds?
I think I know where to find it from here: https://treeherder.mozilla.org/ui/#/jobs?repo=mozilla-inbound Afaik, debug build don't trigger the crash reporter.
(In reply to Martijn Wargers [:mwargers] (QA) from comment #5) > I think I know where to find it from here: > https://treeherder.mozilla.org/ui/#/jobs?repo=mozilla-inbound Awesome! > Afaik, debug build don't trigger the crash reporter. Will try with a local optimized build then. Thanks!
I can't get the crash reporter to open with an optimized build either. Would still like confirmation from the build on inbound but will start looking into it.
Assignee: nobody → spohl.mozilla.bugs
Blocks: 1047584
Status: NEW → ASSIGNED
Flags: needinfo?(martijn.martijn)
Attached patch PatchSplinter Review
Confirmed locally that this fixes the issue.
Attachment #8499158 - Flags: review?(benjamin)
Attachment #8499158 - Flags: review?(benjamin) → review+
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla35
Works again in latest Nightly, thanks.
Status: RESOLVED → VERIFIED
I think that this is a perfect candidate for Moztrap if we don't have a test yet. I do not see a way to get this easily automated, even not with Mozmill. Juan, mind adding it to Moztrap.
Flags: needinfo?(jbecerra)
Flags: in-moztrap?(jbecerra)
Hardware: x86 → All
Flags: needinfo?(jbecerra)
Flags: in-moztrap?(jbecerra) → in-moztrap+
Landed on aurora in the Mac V2 signing combined patch in bug 1047584
Flags: qe-verify+
Reproduced with Nightly 2014-10-02: no Crash Reporter displayed with STR from comment 0 nor from comment 2. Verified as fixed with Firefox 34 beta 7 (Build ID: 20141106201515) on Mac OS X 10.9.5 - the Crash Reporter is shown and all the crashes are properly reported.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: