Closed Bug 574433 Opened 14 years ago Closed 13 years ago

Firefox Sync breaks Firefox 3.6 on OSX

Categories

(Cloud Services :: General, defect)

Product:
Cloud Services
Component:
General
Platform:
x86_64
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: rxt360, Unassigned)

References

Details

(Keywords: qawanted, Whiteboard: [closeme 2010-11-15]) 

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.10) Gecko/20100504 Firefox/3.5.10
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.10) Gecko/20100504 Firefox/3.5.10

Firefox 3.6.4 won't start on my macbook (osx 10.6) after installing Firefox Sync addon. Firefox 3.5.10 does work. 

Reproducible: Always

Steps to Reproduce:
1. remove the profile from the library to start clean
2. install firefox 3.6.4 => this works, restarting works
3. install firefox sync and restart
4. firefox won't start anymore
Same here unfortunately. :(

Downgrading to 3.5.10 serves as a temporary workaround here, too.

Is there anything we could do to provide data to pin down the bug? Can I start Firefox in debug mode? Where can I find logs that could give more information?
I know that on Windows you have some kind of safe mode. 
http://kb.mozillazine.org/Safe_mode

This disables all plugins. Disable the sync addon, and the problem is gone, so that wouldn't be a good way to find out the cause. 

You could remove the sync addon (if it's not essential for you), then upgrade. I haven't tried that with all addons and user data myself, but I guess that could work.
Component: Extension Compatibility → Needs Triage
Product: Firefox → Weave
QA Contact: extension.compatibility → needstriage
Safe mode is also available on OS X if Firefox is run from the command line:
http://kb.mozillazine.org/Safe_mode#Mac_OS_X

The problem is: after 3.6 once crashed in that way, it's impossible to start it again using this profile (tried with a new profile; it becomes unusable after installing Firefox Sync). Even after uninstalling Sync (using the 3.5.* instance), I am not able to use that profile with 3.6.*.

The very same profile works perfectly fine with Firefox 3.5.* on the Mac.

I have 3 Firefox instances connected/synchronizing with my Firefox Sync account: 3.6.4 on Windows, 3.6.3 on Linux (Ubuntu) and 3.5.10 on OS X.

I'd highly appreciate if someone could give me directions on how to create a meaningful trace log while reproducing this bug. Thanks.
Keywords: qawanted
This morning I managed to get 3.6.4 up and running with my existing profile, including the Sync add-on.

I am still unsure if this issue is really related to the Sync add-on.

Usually, Firefox.app resides in a sub-folder of /Applications where only admin users have write access (the user account I'm using is not in the admin group). After I copied Firefox.app to my ~/Desktop/ folder I was able to start it. It ran the add-on compatibility check and seems to work correctly now.

I monitored the system logs but saw no message related to Firefox.

Does the add-on compatibility check need write permissions for the Firefox.app folder?

I will try to reproduce the buggy behavior if possible.
For me that doesn't work. Firefox 3.6.4 started from the desktop folder does the compatibility check, then quits.
… and it's gone again.

Updated from 3.6.4 -> 3.6.6 using the integrated update mechanism of Firefox. Compatibility check. Boom.

The syslog only reads:

27.06.10 18:05:30	com.apple.launchd.peruser.502[147]	([0x0-0xfb0fb].org.mozilla.firefox[3400]) Exited with exit code: 1
You mean that it doesn't run from the desktop folder? For me, 3.6.6 doesn't work.
After the update, I am neither able to open Firefox.app on the Desktop nor in the Applications folder.

3.6 starts if I hold the Option key during startup (going into safe mode) and disable all add-ons.

I tried to activate them one after another, one by one. Firefox crashed on me the first time after the 5th add-on I activated (which was not Sync). After disabling all add-ons and just activating Sync, Firefox crashes on me, too.
I have exactly the same problem. After upgrading to 3.6.6 on Mac OSX Firefox crashes at startup time. I'm able to start it via the console with "-safe-mode" option and to disable all plugins.

I have 4 Extensions installed:
- Adblock Plus 1.2
- Tab Mix Plus 0.3.8.4
- Firefox Sync 1.3.1
- Ubiquity 0.1.9.1

I'm able to activate Adblock Plus and Tab Mix Plus without any problems. But when ANY of Firefox Sync or Ubiquity is activated Firefox crashes at startup time. So this supports the assumption that this is not limited to Firefox Sync but a more general problem.

best regards

Florian
Could someone please change the description of this bug?
It seems to be a problem with the add-on enabling/compatibility checking mechanism in 3.6.* in general for at least two add-ons I used — it is not limited to Firefox Sync only.

I have verified the faulty behavior with the Firefox releases 3.6.4, 3.6.6, 3.6.7a6pre on Mac OS X 10.6.3. They all make Firefox not start once a few add-ons are enabled.

I am currently using these add-ons:
1) Adblock Plus 1.2
2) Firefox PDF Plugin for Mac OS X 1.1.3
3) Firefox Sync 1.4
4) FireGestures 1.5.7
5) Firesizer 1.0.1
6) HTTPS-Everywhere 0.2.1
7) Long URL Please 0.4.3
8) Personas 1.5.3

I am able to enable add-ons 1) and 4) to 8). As soon as I try to enable 2) or 3) Firefox won't start anymore, no matter if other add-ons are enabled or not.

I would *really* like to provide debug information but I am not able to build 3.6.6 from the sources on my Mac, following the instructions on MDN. Has anyone successfully compiled 3.6.6 and could provide me with the .app so I can try to produce debug output? Thanks.
Hi,

after upgrading to Firefox 3.6.8 the problem seems to be gone. I'm now able to activate all extensions including
 - firefox sync
 - ubiquity

best regards

Florian
Hi, I just upgraded to FF 4 beta, and that works too with most addons. Only Brief doesn't work at the moment, but that's not the issue here.
Component: Needs Triage → General
QA Contact: needstriage → general
I just tested against 3.6.9 and it seems like the problem is gone. Can others verify this?
I registered here due to this issue after experiencing this same thing with 3.6.10 when/after updating an extension (Swedish spell-check dictionary). As I'm not as experienced as all of you seem to be in fixing bugs, I'll just settle for the previous version (3.5.13) for now.
If anyone is still seeing this, please take the time to disable your other add-ons one at a time to see if some interaction is in play here.
Whiteboard: [closeme 2010-11-15]
3.6.12 on Mac OS X 10.6.4

Started Firefox with all plugins disabled (pressed the Alt key when starting the application and chose [x] Disable all addons).

Enabled the Sync addon. Restarted Firefox.

Kaboom.

I have the same issue on opensuse11.3 (on two machines). On the first one I did disable all plugins (thats how i worked out it was weave/sync).

After I quit, i cant restart firefox (it dies right away with no output).

As posted in https://bugzilla.mozilla.org/show_bug.cgi?id=574085#c7 , the work-around to get it going again is:

1) start with   firefox --safe-mode
2) hit 'quit' button on safe-mode menu (ie, dont do anything in safemode)
3) restart as normal

Firefox now starts correctly.

Im on opensuse 11.3 (64) with firefox 3.6.12 and sync 1.5.1
Build identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13

Not able to reproduce
Fixed for me by opensuse update to Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13
Reporter, are you still seeing this issue in 4.0.1 or latest nightly?
(In reply to comment #21)
> Reporter, are you still seeing this issue in 4.0.1 or latest nightly?

(This bug isn't applicable to 4.0.1 or latest nightly, since Sync is built-in there.  If this affected Firefox 4.0+, it'd be "Firefox won't start at all ever".)

Resolving as WORKSFORME per comments 18 & 19.  If still reproducible, please reopen.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.