349570 - crash on startup after (failed?)_ update to b2 candidate

Status: RESOLVED WORKSFORME

(Toolkit :: Application Update, defect)

Description

[Mike Shaver (:shaver -- probably not reading bugmail closely)]

Looks like I was applying a full update, not sure what from which build exactly:

<updates xmlns="http://www.mozilla.org/2005/app-update"><update type="minor" name="Bon Echo 2.0b2" version="2.0b2" extensionVersion="2.0b2" detailsURL="http://www.mozilla.com/firefox/releases/" licenseURL="undefined" serviceURL="https://aus2.mozilla.org/update/2/Firefox/2.0b2/2006081806/Darwin_Universal-gcc3/en-US/nightly/Darwin%208.7.1/update.xml" installDate="1156155771999" statusText="Install Pending" buildID="2006082003" isCompleteUpdate="false" channel="nightly"><patch type="complete" URL="http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2006-08-20-03-mozilla1.8/firefox-2.0b2.en-US.mac.complete.mar" hashFunction="sha1" hashValue="38ffd9a9b7ae08484853d83962661c13b4198647" size="16509174" selected="true" state="pending"/></update></updates>

Update looks like it failed (from 0/update.log):

FINISH REMOVE Contents/MacOS/components/myspell/en-US.aff
failed: 6
calling QuitProgressUI

And now on startup I always get:

Thread 0 Crashed:
0   libmozjs.dylib              0x00f56134 js_InflateString + 54
1   libmozjs.dylib              0x00ee4f6b JS_CompileScriptForPrincipals + 33
2   org.mozilla.firefox         0x0007495e mozJSComponentLoader::GlobalForLocation(char c
onst*, nsIFile*, JSObject**) + 2334
3   org.mozilla.firefox         0x00074d10 mozJSComponentLoader::ModuleForLocation(char c
onst*, nsIFile*, unsigned*) + 134
4   org.mozilla.firefox         0x00074fc8 mozJSComponentLoader::GetFactory(nsID const&, 
char const*, char const*, nsIFactory**) + 48
5   libxpcom_core.dylib         0x0184123d nsComponentManagerImpl::CreateInstanceByContra
ctID(char const*, nsISupports*, nsID const&, void**) + 299
6   libxpcom_core.dylib         0x01841b29 nsComponentManagerImpl::GetServiceByContractID
(char const*, nsID const&, void**) + 251
7   libxpcom_core.dylib         0x0180a3a7 CallGetService(char const*, nsID const&, void*
*) + 53
8   libxpcom_core.dylib         0x0180a6c6 nsGetServiceByContractIDWithError::operator()(
nsID const&, void**) const + 30
9   libxpcom_core.dylib         0x0180a2d5 nsCOMPtr_base::assign_from_gs_contractid_with_
error(nsGetServiceByContractIDWithError const&, nsID const&) + 21
10  org.mozilla.firefox         0x0020f403 nsAppStartupNotifier::Observe(nsISupports*, ch
ar const*, unsigned short const*) + 835

Comment 1

[Mike Beltzner [:beltzner, not reading bugmail]]

fwiw, this wfm; anyone else see this?

Comment 2

[J. Paul Reed [:preed]]

*** This bug has been marked as a duplicate of 343037 ***

Comment 3

[J. Paul Reed [:preed]]

Oops... my fat fingers did this... this is most certainly not a dupe.

Comment 4

[Marcia Knous [:marcia]]

PPC Mac: I tested going from the Bon Echo nightly build on 8-18-06 to the beta2 build on the nightly channel (Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1b2) Gecko/20060821 BonEcho/2.0b2), and I did not get a failed update or a crash.

Comment 5

[Mike Shaver (:shaver -- probably not reading bugmail closely)]

Attachment: update.log

Comment 6

[Mike Shaver (:shaver -- probably not reading bugmail closely)]

I'm on Intel, FWIW.  I'll try to test later with a clean profile, if that's desired, though I haven't done anything with extensions or whatnot in quite a while.

Comment 7

[Nick Thomas [:nthomas] (UTC+12)]

Update WFM too from 2006081806 in VMWare.

(Clarifcation: The b2 candidate build (2006082101) isn't on the nightly channel. You're getting an update to the 20060821 nightly here.)

Comment 8

[Mike Shaver (:shaver -- probably not reading bugmail closely)]

I see it with a fresh profile (-profile `pwd`/tmp) as well, I bail with a bus error.

Comment 9

[Mike Beltzner [:beltzner, not reading bugmail]]

Preed mentioned that "error 6" is a "read error", implying that the update file has become corrupted on disk. Looking through shaver's log, I see some "error 5" messages as well. Are these error codes documented anywhere? I don't see them documented in http://wiki.mozilla.org/Software_Update.

There seem to be a large number of read/stat errors in shaver's log as well.

Shaver: when you said you recreated with a clean profile, did you grab the previous nightly and try to update it again? Or just tried to boot with a clean profile? I can do either, assuming you're a little slammed for time :)

Comment 10

[Nick Thomas [:nthomas] (UTC+12)]

Error definitions are in 
http://lxr.mozilla.org/mozilla/source/toolkit/mozapps/update/src/updater/errors.h

Looks like the first and real error is:
 EXECUTE ADD Contents/MacOS/components/nsSidebar.js
 copy_file: failed to read: 5
 ### execution failed

It is normal to have quite a few "PREPARE REMOVE ..." lines for old files which are routinely removed by the updater.

All the "FINISH ADD .." errors follow the FINISH ADD for nsSidebar.js

Comment 11

[Benjamin Smedberg]

Actually the "5" error is what comes from the OS "errno": in this case EIO (Input/Output error), and isn't very specific.

Comment 12

[Mike Beltzner [:beltzner, not reading bugmail]]

16:37 < shaver> disk0s2: 0xe0030005 (UNDEFINED).
16:37 < shaver> disk0s2: 0xe0030005 (UNDEFINED).
16:37 < shaver> disk0s2: 0xe0030005 (UNDEFINED).
16:37 < shaver> _nice_
16:37 <@beltzner> yeah, I'm gonna go resolve your bug WFM :)