Closed Bug 1290503 Opened 8 years ago Closed 8 years ago

Firefox crashes after losing connection and reconnecting

Categories

(Core :: Storage: IndexedDB, defect)

51 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1275518

People

(Reporter: samy.sadi.contact, Unassigned)

Details

Attachments

(1 file)

Attached file stacktrace.txt
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0 Build ID: 20160728030208 Steps to reproduce: Open firefox and some webpages. Disable wifi for instance. Reactivate wifi after 2 or 3 minutes. Using archlinux x86_64 with xfce. Actual results: Firefox crashes after a small delay (some seconds). On console I see this: console.error: PushService: stateChangeProcessEnqueue: Error transitioning state UnknownError console.error: Error in asyncStorage.setItem(): console.error: Error in asyncStorage.setItem(): console.error: Error in asyncStorage.setItem(): ExceptionHandler::GenerateDump cloned child 8940 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... [Child 6652] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-cen-l64-ntly-000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2056 [Child 6652] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-cen-l64-ntly-000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2056
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Has STR: --- → yes
is crash reporter enabled on your build? if so, can you provide crash report? that will give us some more info for the backtrace, especially symbols.
Flags: needinfo?(samy.sadi.contact)
The crash reporter is enabled. However, for some strange reason I cannot reproduce the issue anymore (I suspect recent system update). As a notice, I used to experience the issue for several months and very consistently after disconnections on previous versions too (i.e. 46 and 47, and then on 50). Anyways, I will provide additional information as soon as I reproduce the issue.
Version: 50 Branch → 51 Branch
Here is the crash ID (note crash reported using ver. 51). db57a5fe-e3aa-446b-9f02-1b63e2160806
the crash signature is reported only once. If you have experienced the crash several times and reported them also, that's strange.
Flags: needinfo?(samy.sadi.contact)
Believe me, I experience the same crash several times a week. It's just that I reported it only now.
(In reply to Samy from comment #5) > It's just that I reported it only now. ah, that explains. bug 1264853 and bug 1275518 might be related.
Component: Untriaged → DOM: IndexedDB
Product: Firefox → Core
Hi Bevis, Do you have any ideas of this?
Flags: needinfo?(btseng)
The crash report of comment 4 looks related to bug 1275518.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(btseng)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: