959554 - *** ERROR addons.xpi: Failed to process extension changes at startup: Error: couldn't find function symbol in library (resource://gre/modules/osfile/osfile_unix_allthreads.jsm:68)

Status: RESOLVED DUPLICATE of bug 960509

(Core :: General, defect)

Description

[sci-fi]

This line is presented on console when Nightly/trunk is first started.  It started after the trunk m-c tinderbox builds past 34697b7131dd (20140113143835) [which is good/usable itself, I'm using it now ;) ].

The GUI becomes messed-up and unusable.  Even some/most/all keyboard shortcuts won't work properly -- must use mouse to close a window or quit the app (via pull-down menu), for examples.

I've tried -safe-mode, too, same thing.

(I must use OSX 10.6/SnowLeopard in 32-bit mode [EFI/BIOS limits] even though this iMac contains a Core-2-Duo and can/does run apps in 64-bit mode [I still have 32-bit-only plugins that don't show-up with FF in 64-bit mode] … long story.)

Comment 1

[sci-fi]

Hi,

This bug continues with the current m-c tinderbox builds (I just tested rev=81bced59e8b3 buildid=20140114154434 which is tip/head as of this writing).

Now this bug has entered into the Thunderbird/Daily c-c tinderbox builds (I just tested buildid=20140114070802 rev=76d9545cff20 which incorporates m-c rev=3a264db9f9e7, latest build as of this writing).

The last good Thunderbird/Daily for me is at buildid=20140113070346 rev=0456c50549f6 (m-c rev=0456c50549f6).

For completeness, the last good Firefox/Nightly for me is buildid=20140113143835 rev=34697b7131dd.

Should I raise this bug via the nightly mail-list?  I'm afraid other testers will be seeing this bug (I hope <w>).

Thanks.

Comment 2

[sci-fi]

Hi,

This bug shows up when started in 32-bit mode only -- both Firefox/Nightly and Thunderbird/Daily.  When I let them start in 64-bit mode (default on most systems), the bug does not show.  [I can switch these modes since I run 10.6/SL with a Core-2-Duo, 32-bit EFI/BIOS does not matter.)  AAMOF I am running the current tip/head tinderbox builds right now as I type this update (and yes 32-bit mode still shows the bug at this level).

This means, of course, that 10.6/SL systems without a 64-bit-capable CPU will be totally out of luck (e.g. Core-Duo and such).

So it seems some patch soon after 34697b7131dd is causing builds to miss some 32-bit code somehow to cause this bug.  Surely the tinderbox buildlogs would mention such a problem?

I suppose I will need to live with the loss of 32-bit-only plugins and such (no biggee for me).  But it seems no-one else is testing 32-bit modes on OSX?

I don't know what else to do but to alert via this bug.