Crash in [@ RefPtr<T>::get | RefPtr<T>::operator-> | JS::loader::ScriptLoadRequest::GetWorkerLoadContext]
Categories
(Core :: DOM: Workers, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox107 | --- | unaffected |
firefox108 | --- | unaffected |
firefox109 | --- | fixed |
People
(Reporter: gsvelto, Assigned: yulia)
References
(Regression)
Details
(Keywords: crash, regression)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/36930dc3-bd52-4dbf-b9a0-033fc0221121
Reason: EXCEPTION_ACCESS_VIOLATION_READ
Top 10 frames of crashing thread:
0 xul.dll RefPtr<JS::loader::LoadContextBase>::get const mfbt/RefPtr.h:286
0 xul.dll RefPtr<JS::loader::LoadContextBase>::operator-> const mfbt/RefPtr.h:316
0 xul.dll JS::loader::ScriptLoadRequest::GetWorkerLoadContext js/loader/ScriptLoadRequest.cpp:152
0 xul.dll mozilla::dom::ThreadSafeRequestHandle::GetContext dom/workers/loader/WorkerLoadContext.h:170
0 xul.dll mozilla::dom::workerinternals::loader::NetworkLoadHandler::DataReceivedFromNetwork dom/workers/loader/NetworkLoadHandler.cpp:68
1 xul.dll mozilla::dom::workerinternals::loader::NetworkLoadHandler::OnStreamComplete dom/workers/loader/NetworkLoadHandler.cpp:58
2 xul.dll mozilla::net::nsStreamLoader::OnStopRequest netwerk/base/nsStreamLoader.cpp:85
3 xul.dll mozilla::net::nsStreamListenerTee::OnStopRequest netwerk/base/nsStreamListenerTee.cpp:51
4 xul.dll mozilla::net::nsHTTPCompressConv::OnStopRequest netwerk/streamconv/converters/nsHTTPCompressConv.cpp:180
5 xul.dll std::_Func_impl_no_alloc<`lambda at /builds/worker/checkouts/gecko/netwerk/protocol/http/HttpChannelChild.cpp:799:13', void>::_Do_call netwerk/protocol/http/HttpChannelChild.cpp:1052
This was detected by the crash spike reporter, it's a NULL pointer access. The affected code was touched by bug 1800496 so this is most likely a regression from that bug. Yulia can you have a look please?
Updated•2 years ago
|
Comment 1•2 years ago
|
||
(In reply to Gabriele Svelto [:gsvelto] from comment #0)
The affected code was touched by bug 1800496 so this is most likely a regression from that bug.
Just to be clear: This is true for the recent nightly instances >= 20221118...
. The old spike from 106 release can be ignored here.
Reporter | ||
Comment 2•2 years ago
|
||
Yes, thanks Jens. The crash signature here is too generic, I'll open a bug to improve it.
Comment 3•2 years ago
|
||
Set release status flags based on info from the regressing bug 1800496
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Description
•