Closed Bug 1882873 Opened 2 years ago Closed 2 years ago

Crash in [@ memcpy | mozilla::detail::Endian<T>::read<T>]

Categories

(Core :: Networking: DNS, defect)

Unspecified
Linux
defect

Tracking

()

RESOLVED DUPLICATE of bug 1884628

People

(Reporter: RyanVM, Unassigned)

References

Details

(Keywords: crash, topcrash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/dbfd4920-eb1e-4abb-bd3f-3a2c40240229

Reason: SIGBUS / BUS_ADRERR

Top 10 frames of crashing thread:

0  libxul.so  memcpy  /builds/worker/fetches/sysroot-x86_64-linux-gnu/usr/include/x86_64-linux-gnu/bits/string3.h:51
0  libxul.so  mozilla::detail::Endian<  mfbt/EndianUtils.h:520
0  libxul.so  mozilla::detail::Endian<  mfbt/EndianUtils.h:289
0  libxul.so  mozilla::loader::InputBuffer::codeUint32  js/xpconnect/loader/IOBuffers.h:104
0  libxul.so  mozilla::dom::ipc::SharedMap::MaybeRebuild  dom/ipc/SharedMap.cpp:219
1  libxul.so  mozilla::dom::ipc::SharedMap::Get  dom/ipc/SharedMap.cpp:58
1  libxul.so  mozilla::dom::ipc::SharedMap::Get  dom/ipc/SharedMap.h:77
1  libxul.so  mozilla::dom::MozSharedMap_Binding::get  dom/bindings/MozSharedMapBinding.cpp:165
2  libxul.so  mozilla::dom::binding_detail::GenericMethod<mozilla::dom::binding_detail::NormalThisPolicy, mozilla::dom::binding_detail::ThrowExceptions>  dom/bindings/BindingUtils.cpp:3258
3  libxul.so  CallJSNative  js/src/vm/Interpreter.cpp:480

The bug is linked to a topcrash signature, which matches the following criterion:

  • Top 10 desktop browser crashes on nightly

For more information, please visit BugBot documentation.

Keywords: topcrash

I've got two waves of this crash. It happened after I suspended my system overnight while nightly was running. After two three tabs, tabs were crashing consistently (except for about:crashes) until I restarted nightly. It didn't happen for short time suspension.

Component: MFBT → IPC

There's a bug that was introduced with the patch for bug 1853497, and fixed when it was backed out in bug 1884628, which could indirectly cause problems like this. I notice that the latest build ID where we see this crash signature is 20240311092833, which is also the last build before bug 1884628 landed (see “first release with” / “last release without” for the commit).

I'm going to close this as a duplicate of bug 1884628, but it can be reopened if it's observed on newer builds.

Status: NEW → RESOLVED
Closed: 2 years ago
Component: IPC → Networking: DNS
Duplicate of bug: 1884628
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.