Closed Bug 486149 Opened 16 years ago Closed 16 years ago

Weave 3.0 causes Firefox to crash if "sync on quit" is enabled

Categories

(Cloud Services :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: liquidsunshine, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3 Build Identifier: 3.0 If the "extensions.weave.syncOnQuit.enabled" option is set to true, Firefox will crash on quit. If it is set to false, it closes cleanly. I'm using this version of Firefox: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3 on Arch Linux. Reproducible: Always Steps to Reproduce: 1. Have the "extensions.weave.syncOnQuit.enabled" option set to true. 2. Try to close Firefox. 3. The browser crashes and displays the "send crash information to mozilla" box. Actual Results: The browser crashes. Expected Results: The browser syncs and quits cleanly.
Blocks: 486261
Sync on quit pref is not exposed anywhere, downgrading from critical.
Severity: critical → normal
OS: Linux → All
Hardware: x86 → All
I am not sure if this is related. Being very reluctant to start a new bug, I put my comment here. Using: Firefox 3.1b3 on Intel Mac 10.4.11 and Minefield 3.6a1pre on Windows XP Signs: Firefox crashes within minutes of opening even if there is no activity beyond opening the home page. Weave tries to sync and after a while, the browser crashes. Workaround: Immediately after opening Firefox, either disable Weave or go to Weave preferences and uncheck "Automatically connect each time I start Firefox". Solution: Not available as far as I know NOTE TO READERS: If I need to move it to its own bug, please let me know. (Or better still, if you experience it too, do it yourself!)
We no longer do sync on quit, so closing.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Component: Weave → General
Product: Mozilla Labs → Weave
Target Milestone: -- → ---
QA Contact: weave → general
You need to log in before you can comment on or make changes to this bug.