Crashes in objc_msgSend | (anonymous namespace)::AutoreleasePoolPage::pop in nsAppShell::AfterProcessNextEvent()
Categories
(Core :: Widget: Cocoa, defect)
Tracking
()
People
(Reporter: smichaud, Unassigned)
References
Details
Crash Data
These have been around for a while, but have recently increased in frequency. They all happen accessing memory at 0xffffffffe5e5e5f8.
Typical top of stack trace:
0 libobjc.A.dylib objc_msgSend context
1 libobjc.A.dylib (anonymous namespace)::AutoreleasePoolPage::pop(void*) frame_pointer
2 CoreFoundation __CFStringEncodeByteStream frame_pointer
3 Foundation -[NSAutoreleasePool release] frame_pointer
4 XUL nsAppShell::AfterProcessNextEvent(nsIThreadInternal*, bool) widget/cocoa/nsAppShell.mm:808 frame_pointer
5 XUL nsThread::ProcessNextEvent(bool, bool*) xpcom/threads/nsThread.cpp:1278 frame_pointer
6 XUL NS_ProcessPendingEvents(nsIThread*, unsigned int) xpcom/threads/nsThreadUtils.cpp:434 frame_pointer
7 XUL nsBaseAppShell::NativeEventCallback() widget/nsBaseAppShell.cpp:87 frame_pointer
8 XUL nsAppShell::ProcessGeckoEvents(void*) widget/cocoa/nsAppShell.mm:440 frame_pointer
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 1•5 years ago
|
||
This bug might benefit from an analysis using a HookCase hook library (https://github.com/steven-michaud/HookCase).
Reporter | ||
Comment 2•5 years ago
|
||
Possibly related to bug 1587351, which also happens in nsAppShell::AfterProcessNextEvent().
Comment 3•5 years ago
|
||
This crash spikes in Nightly 20191008214557 and then drops to zero. The changes that were causing bug 1587351 were in that version afaik. It's possible this is something else, but if it's the same crash as bug 1587351 then this has already been backed out.
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 4•5 years ago
|
||
(In reply to comment #3)
Yes, this is probably a dup of bug 1587351. But let's keep it separate for the time being, until further investigation shows it has the same cause.
Reporter | ||
Updated•5 years ago
|
Comment 5•5 years ago
|
||
The priority flag is not set for this bug.
:spohl, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 6•5 years ago
|
||
The reported spike in crashes correlates to the spike in bug 1587351.
Description
•