Closed
Bug 517492
Opened 15 years ago
Closed 15 years ago
Sync will not complete, causing firefox not to quit successfully
Categories
(Firefox :: Sync, defect, P1)
Tracking
()
VERIFIED
FIXED
0.8
People
(Reporter: cohesion, Assigned: Mardak)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 If I leave firefox open for too long a sync will happen that will not complete. If this happens, when I quit FF, it seems like it quit ok, but firefox.exe is still running. When you re-open it you get the normal "already running" error. Reproducible: Sometimes Steps to Reproduce: 1. Open firefox 2. Wait for a sync that never stops 3. Quit firefox Actual Results: Firefox.exe stays running preventing re-launch Expected Results: firefox.exe will quit
Assignee | ||
Comment 1•15 years ago
|
||
Most likely sync-async keeping the loop spinning. We should listen for app shutdown? And push it to jsmodules too.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking-weave1.0+
Assignee | ||
Updated•15 years ago
|
Target Milestone: --- → 0.8
Assignee | ||
Comment 2•15 years ago
|
||
http://hg.mozilla.org/labs/weave/rev/881eb9a527b4 Lazily listen for quit-application on the first sync-async call and bail out if the notification is sent while waiting for the callback. Should probably add a test and land this on the js modules repository if this method of checking for app-quit is okay.
Assignee: nobody → edilee
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•15 years ago
|
Priority: -- → P1
Comment 3•14 years ago
|
||
flagging in-testsuite? for unit tests to cover. Manually verified fix on weave 1.3b5
Status: RESOLVED → VERIFIED
Flags: in-testsuite?
Updated•6 years ago
|
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in
before you can comment on or make changes to this bug.
Description
•