Crash in [@ huge_dalloc | MozJemalloc::free | free | rlbox::rlbox_wasm2c_sandbox::impl_create_sandbox]
Categories
(Core :: Security: RLBox, defect)
Tracking
()
People
(Reporter: michideep, Unassigned)
Details
Steps to reproduce:
- Go to https://issmmbeatenyet.com
- Mash the "NOT YET" logo
- The tab will crash after about 17-40 taps
This also happens on nightly 125.0a1.
Crash report: https://crash-stats.mozilla.org/report/index/bd99e119-d92d-48e2-96b7-11c320240316
MOZ_CRASH Reason: MOZ_RELEASE_ASSERT(node) (Double-free?)
Top 10 frames of crashing thread:
0 libmozglue.so huge_dalloc memory/build/mozjemalloc.cpp:4295
1 libmozglue.so MozJemalloc::free memory/build/malloc_decls.h:54
1 libmozglue.so free memory/build/malloc_decls.h:54
2 liblgpllibs.so rlbox::rlbox_wasm2c_sandbox::impl_create_sandbox media/libsoundtouch/src/RLBoxSoundTouch.cpp
2 liblgpllibs.so rlbox::rlbox_sandbox<rlbox::rlbox_wasm2c_sandbox>::create_sandbox<bool> third_party/rlbox/include/rlbox_sandbox.hpp:402
2 liblgpllibs.so mozilla::RLBoxSoundTouch::RLBoxSoundTouch media/libsoundtouch/src/RLBoxSoundTouch.cpp:15
3 libxul.so mozilla::AudioDecoderInputTrack::EnsureTimeStretcher dom/media/mediasink/AudioDecoderInputTrack.cpp:623
3 libxul.so mozilla::AudioDecoderInputTrack::AppendTimeStretchedDataToSegment dom/media/mediasink/AudioDecoderInputTrack.cpp:424
3 libxul.so mozilla::AudioDecoderInputTrack::AppendBufferedDataToOutput dom/media/mediasink/AudioDecoderInputTrack.cpp:390
3 libxul.so mozilla::AudioDecoderInputTrack::ProcessInput dom/media/mediasink/AudioDecoderInputTrack.cpp:343
Comment 1•2 years ago
|
||
mozregession with GeckoviewExample (arm64) result:
It looks related to bug 1853840
Also this seems not reproducible on GeckoviewExample (x86_64)
Updated•2 years ago
|
Comment 2•2 years ago
|
||
The severity field is not set for this bug.
:shravanrn, could you have a look please?
For more information, please visit BugBot documentation.
Comment 3•2 years ago
|
||
Sorry for the delay here. Will investigate. I think this could be a dup which is now fixed. Will investigate and confirm in the next day or so.
Comment 4•2 years ago
|
||
Yup, this is a dup. The prior bug partially addresses the problem. But, we still need to provide a more graceful fallback to OOM, but we can track this as a separate feature.
Description
•