Closed
Bug 1529623
Opened 7 years ago
Closed 7 years ago
Crash in [@ AsyncShutdownTimeout | places.sqlite#1: waiting for clients | places.sqlite#1: Bookmarks.jsm: fetchBookmarksByURL (33)]
Categories
(Firefox :: Bookmarks & History, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: superman.jason, Unassigned)
Details
Crash Data
This bug is for crash report bp-2a8cff1b-06dd-48b7-985d-14f030190219.
Top 10 frames of crashing thread:
0 firefox <name omitted> /builddir/build/BUILD/firefox-65.0/memory/mozalloc/mozalloc_abort.cpp:33
1 libxul.so <name omitted> /builddir/build/BUILD/firefox-65.0/xpcom/base/nsDebugImpl.cpp:438
2 libxul.so <name omitted> /builddir/build/BUILD/firefox-65.0/xpcom/base/nsDebugImpl.cpp:133
3 libxul.so NS_InvokeByIndex
4 libxul.so XPCWrappedNative::CallMethod [clone .constprop.14614] /builddir/build/BUILD/firefox-65.0/js/xpconnect/src/XPCWrappedNative.cpp:1645
5 libxul.so <name omitted> /builddir/build/BUILD/firefox-65.0/js/xpconnect/src/XPCWrappedNativeJSOps.cpp:948
6 libxul.so <name omitted> /builddir/build/BUILD/firefox-65.0/js/src/vm/Interpreter.cpp:443
7 libxul.so <name omitted> /builddir/build/BUILD/firefox-65.0/js/src/vm/Interpreter.cpp:594
8 libxul.so <name omitted> /builddir/build/BUILD/firefox-65.0/js/src/vm/Interpreter.cpp:423
9 libxul.so <name omitted> /builddir/build/BUILD/firefox-65.0/js/src/vm/Interpreter.cpp:563
Comment 1•7 years ago
|
||
This crash is not common in our signatures, there may be something wrong with your profile or the system was busy with something else and couldn't complete Firefox shutdown in a minute.
This kind of crash is benign, basically if Firefox process doesn't close in a meaningful amount of time, we crash it.
What I may suggest is to run a Database Integrity from about:support to ensure the database is sane... Apart from that, there isn't much we can do here...
Unfortunately for now it's not actionable, we'll work on bugs to get better metadata about these crashes.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•