1840528 - Startup Crash in [@ mozilla::net::CacheIndexEntry::CacheIndexEntry]

Status: RESOLVED INCOMPLETE

(Core :: Networking: Cache, defect, P2)

Description

[Wayne Mery (:wsmwk)]

Crash report: https://crash-stats.mozilla.org/report/index/1894c77b-1b13-4ac4-8c5d-7a8850230623

Reason: EXCEPTION_ACCESS_VIOLATION_WRITE

Top 10 frames of crashing thread:

0  xul.dll  mozilla::net::CacheIndexEntry::CacheIndexEntry  netwerk/cache2/CacheIndex.h:131
1  xul.dll  already_AddRefed<mozilla::net::CacheFileHandle>::already_AddRefed  mfbt/AlreadyAddRefed.h:52
1  xul.dll  RefPtr<mozilla::net::CacheFileHandle>::forget  mfbt/RefPtr.h:298
1  xul.dll  mozilla::net::CacheFileHandles::NewHandle  netwerk/cache2/CacheFileIOManager.cpp:424
2  xul.dll  mozilla::net::CacheFileIOManager::OpenFileInternal  netwerk/cache2/CacheFileIOManager.cpp:1728
3  xul.dll  mozilla::net::OpenFileEvent::Run  netwerk/cache2/CacheFileIOManager.cpp:674
4  xul.dll  mozilla::net::CacheIOThread::LoopOneLevel  netwerk/cache2/CacheIOThread.cpp:481
5  xul.dll  mozilla::net::CacheIOThread::ThreadFunc  netwerk/cache2/CacheIOThread.cpp:418
6  xul.dll  mozilla::net::CacheIOThread::ThreadFunc  netwerk/cache2/CacheIOThread.cpp:360
7  nss3.dll  _PR_NativeRunThread  nsprpub/pr/src/threads/combined/pruthr.c:399

Comment 1

[Magnus Melin [:mkmelin]]

Sorry, no idea.

Comment 2

[Wayne Mery (:wsmwk)]

Quite rare.

Other crashes

• mozilla::net::CacheFileHandle::CacheFileHandle bp-062547d0-006f-46ec-a989-52ea50230613
• mozilla::net::CacheFileHandles::NewHandle bp-14b97dc3-1502-4caa-a343-cdfc20230601

Comment 3

[Kershaw Chang [:kershaw]]

Looks like there were 4 crashes coming from the same user. The crash address are all the same 0x0000000000000029.
I'll put this in our queue and monitor it.

Comment 4

[Kershaw Chang [:kershaw]]

Let's monitor this longer.
This recent report seems to be caused by a faulty hardware.

Comment 5

[edgul]

Newer similar report, could this be hardware as well?
https://crash-stats.mozilla.org/report/index/0d31ce5d-5211-4503-bc5c-8bf870231113

Comment 6

[Kershaw Chang [:kershaw]]

(In reply to Ed Guloien [:edgul] from comment #5)

Newer similar report, could this be hardware as well?
https://crash-stats.mozilla.org/report/index/0d31ce5d-5211-4503-bc5c-8bf870231113

No, looks like it's not the same crash. However, it's still not actionable to me.

Also, looking at the latest two crashes, it seems that these two crashes happened on the same user, so it's probably a hardware issue as well.

I think we can close this bug, since these crashes are rare and not actionable.