Closed
Bug 1983397
Opened 1 year ago
Closed 1 year ago
Crash in [@ mozilla::HashStringKnownLength<T>]
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
INCOMPLETE
| Tracking | Status | |
|---|---|---|
| firefox144 | --- | affected |
People
(Reporter: release-mgmt-account-bot, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/772192cf-b9b3-4193-9b4a-507310250814
Reason: SIGSEGV / SEGV_MAPERR
Top 10 frames of crashing thread:
0 libxul.so mozilla::HashStringKnownLength<unsigned char const*> mfbt/HashFunctions.h:268
0 libxul.so mozilla::HashString mfbt/HashFunctions.h:288
0 libxul.so mozilla::HashString xpcom/ds/nsHashKeys.h:39
0 libxul.so nsCStringHashKey::HashKey xpcom/ds/nsHashKeys.h:223
0 libxul.so nsTHashtable<nsBaseHashtableET<nsCStringHashKey, std::unique_ptr<nsTArray<nsCOMPtr<nsIWeakReference> >, mozilla::DefaultDelete<nsTArray<nsCOMPtr<nsIWeakReference> > > > > >::s_HashKey xpcom/ds/nsTHashtable.h:697
1 libxul.so PLDHashTable::ComputeKeyHash const xpcom/ds/PLDHashTable.cpp:479
1 libxul.so PLDHashTable::Search const xpcom/ds/PLDHashTable.cpp:500
2 libxul.so nsTHashtable<nsBaseHashtableET<nsCStringHashKey, std::unique_ptr<nsTArray<nsCOMPtr<nsIWeakReference> >, mozilla::DefaultDelete<nsTArray<nsCOMPtr<nsIWeakReference> > > > > >::GetEntry const xpcom/ds/nsTHashtable.h:291
2 libxul.so nsClassHashtable<nsCStringHashKey, nsTArray<nsCOMPtr<nsIWeakReference> > >::Get const xpcom/ds/nsClassHashtable.h:108
2 libxul.so mozilla::net::nsHttpConnectionMgr::FindCoalescableConnectionByHashKey netwerk/protocol/http/nsHttpConnectionMgr.cpp:712
By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:
- First crash report: 2025-06-29
- 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•1 year ago
|
||
The crash volume is not very high and these don't look actionable.
Status: NEW → RESOLVED
Closed: 1 year ago
Component: General → XPCOM
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•