Open Bug 1938828 Opened 2 months ago Updated 2 months ago

Crash in [@ js::ElementSpecific<T>::initFromIterablePackedArray]

Categories

(Thunderbird :: Account Manager, defect)

Thunderbird 128
Unspecified
Windows 11
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: o.keitel, Unassigned)

Details

New install on Win11.
Everytime I try to send an Email it crashes.

Pasting one of the crash logs below, other ones here:
https://crash-stats.mozilla.org/report/index/f6a3c9a0-f4b2-4095-b637-c2e910241222
https://crash-stats.mozilla.org/report/index/3220beb0-9e15-46a9-86b3-c5d4f0241222

Crash report: https://crash-stats.mozilla.org/report/index/d3b34f57-00f4-4c2f-bf8c-1716e0241222

Reason:

EXCEPTION_ACCESS_VIOLATION_WRITE

Top 10 frames:

0  xul.dll  js::ElementSpecific<signed char, js::UnsharedOps>::initFromIterablePackedArra...  js/src/vm/TypedArrayObject-inl.h:590
1  ?  @0x0000029e9ba4a427
2  xul.dll  (anonymous namespace)::TypedArrayObjectTemplate<unsigned char>::create(JSCont...  js/src/vm/TypedArrayObject.cpp:534
2  xul.dll  (anonymous namespace)::TypedArrayObjectTemplate<unsigned char>::class_constru...  js/src/vm/TypedArrayObject.cpp:494
3  xul.dll  CallJSNative(JSContext*, bool (*)(JSContext*, unsigned int, JS::Value*), js::...  js/src/vm/Interpreter.cpp:481
3  xul.dll  CallJSNativeConstructor(JSContext*, bool (*)(JSContext*, unsigned int, JS::Va...  js/src/vm/Interpreter.cpp:497
3  xul.dll  InternalConstruct(JSContext*, js::AnyConstructArgs const&, js::CallReason)  js/src/vm/Interpreter.cpp:703
4  xul.dll  js::ConstructFromStack(JSContext*, JS::CallArgs const&, js::CallReason)  js/src/vm/Interpreter.cpp:750
4  xul.dll  js::Interpret(JSContext*, js::RunState&)  js/src/vm/Interpreter.cpp:3175
5  xul.dll  MaybeEnterInterpreterTrampoline(JSContext*, js::RunState&)  js/src/vm/Interpreter.cpp:395

UPDATE:
Working fine (i.e. no crash) after a reinstall.

I'm not sure what's usus here so I'll leave this open just in case until a maintainer/collaborater comes along and can close if appropriate.
Thanks.

You need to log in before you can comment on or make changes to this bug.