Crash in [@ __libc_assert_fail]
Categories
(Core :: Memory Allocator, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox131 | --- | affected |
People
(Reporter: release-mgmt-account-bot, Unassigned, NeedInfo)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/54b30b16-add8-4907-bd98-626800240727
Reason: SIGABRT / SI_TKILL
Top 10 frames of crashing thread:
0 libc.so.6 __pthread_kill_implementation nptl/nptl/pthread_kill.c:44
1 libc.so.6 __GI_raise sysdeps/posix/raise.c:26
2 libc.so.6 __GI_abort stdlib/stdlib/abort.c:79
3 libc.so.6 __libc_message_impl sysdeps/posix/libc_fatal.c:132
4 libc.so.6 __libc_assert_fail assert/assert/__libc_assert_fail.c:31
5 libc.so.6 __GI___pthread_mutex_lock nptl/nptl/pthread_mutex_lock.c:167
6 firefox-bin Mutex::Lock memory/build/Mutex.h:94
6 firefox-bin MaybeMutex::Lock memory/build/Mutex.h:204
6 firefox-bin AutoLock<MaybeMutex>::AutoLock memory/build/Mutex.h:251
6 firefox-bin arena_t::MallocSmall memory/build/mozjemalloc.cpp:3449
By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:
- First crash report: 2024-07-27
- Process type: Multiple distinct types
- Is startup crash: No
- Has user comments: No
- Is null crash: Yes - 1 out of 3 crashes happened on null or near null memory address
Comment 1•2 years ago
|
||
This signature is not useful. 2 of the recent crashes are in jemalloc, while another one is in pulse audio.
Comment 2•2 years ago
|
||
Gabriele, any ideas of what we should do with __libc_assert_fail? Thanks.
Comment 3•2 years ago
|
||
The volume looks very low so we can probably just ignore this.
Comment 4•2 years ago
|
||
Yeah, the crashes aren't consistent and the volume is minuscule. Not much we can do.
| Reporter | ||
Comment 5•2 years ago
|
||
The severity field is not set for this bug.
:plawless, could you have a look please?
For more information, please visit BugBot documentation.
Updated•2 years ago
|
| Reporter | ||
Comment 6•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Memory Allocator' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 8•11 months ago
|
||
NI? myself to check the contents of the Mutex header in all of these crashes. This should help me figure out if it's random corruption or if there's a pattern that's leading to this.
| Reporter | ||
Comment 9•11 months ago
|
||
The severity field for this bug is set to S4. However, the following bug duplicate has higher severity:
- Bug 1991622: S3
:pbone, could you consider increasing the severity of this bug to S3?
For more information, please visit BugBot documentation.
Updated•11 months ago
|
Description
•