Closed Bug 611075 Opened 15 years ago Closed 15 years ago

[10.5] After update from Firefox 4 B6->B7 Firefox crashes when the updater launches it

Categories

(Toolkit :: Application Update, defect)

x86
macOS
defect
Not set
critical

Tracking

()

RESOLVED WONTFIX

People

(Reporter: marcia, Unassigned)

Details

(Keywords: relnote, reproducible)

Seen while testing updates on 10.5 Intel Machine. STR: 1. Download a fresh Beta 6 build from the releases directory. 2. Tweak the channel to releasetest 3. Download the update and apply it. Actual: Crash - I get the Apple Crash Reporter Expected: Firefox would launch The next time I launch Firefox it launches fine. Process: firefox-bin [307] Path: /Users/mozilla/Desktop/b6/Firefox.app/Contents/MacOS/firefox-bin Identifier: firefox-bin Version: ??? (???) Code Type: X86-64 (Native) Parent Process: launchd [1] Interval Since Last Report: 103422 sec Crashes Since Last Report: 1 Per-App Interval Since Last Report: 0 sec Per-App Crashes Since Last Report: 1 Date/Time: 2010-11-10 10:47:45.349 -0800 OS Version: Mac OS X 10.5.8 (9L31a) Report Version: 6 Anonymous UUID: F867FE97-7CB5-4BA9-8155-E96E5EED0BC9 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000002, 0x0000000000000000 Crashed Thread: 0 Dyld Error Message: unknown required load command 0x80000022
Summary: [10.5] Update from Firefox 4 B6->B7 crashes when the update is being applied → [10.5] After update from Firefox 4 B6->B7 Firefox crashes when the updater launches it
This is due to 10.5 preferring x86_64 over i386 and Firefox x86_64 not being compatible with 10.5. Bug 600362 solves this going forward and I believe will be backported so official releases won't crash. For b6 to b7 the solution would be to update b6 to a build that only contains the fix from bug 600362 and then update them to b7 but I believe it was decided that the extra work wasn't worth it.
That's exactly right, this should only affect nightly/beta users that made the transition (OKed in bug 601660). For release users, we're backporting bug 600362 to 1.9.2/1.9.1 so this won't be an issue.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.