1901751 - Crash in [@ _ZN3hwy6N_NEONL5LoadUINS0_4SimdIfLm4ELi0EEETnPNS_9EnableIfTIXeqmlsrT_13kPrivateLanesstNS5_1TELi16EEE4typeELPv0ETnPNS4_IXcl6IsSameIS6_fEEEE4typeELSA_0EEENS0_6Vec128IfLm4EEES5_PKf]

Status: RESOLVED DUPLICATE of bug 1901700

(Core :: Graphics: ImageLib, defect)

Description

[BugBot [:suhaib / :marco/ :calixte]]

Crash report: https://crash-stats.mozilla.org/report/index/a402647e-0854-431c-a804-3113f0240610

Reason: EXC_BAD_ACCESS / KERN_PROTECTION_FAILURE

Top 10 frames of crashing thread:

0  XUL  _ZN3hwy6N_NEONL5LoadUINS0_4SimdIfLm4ELi0EEETnPNS_9EnableIfTIXeqmlsrT_13kPrivateLanesstNS5_1TELi16EEE4typeELPv0ETnPNS4_IXcl6IsSameIS6_fEEEE4typeELSA_0EEENS0_6Vec128IfLm4EEES5_PKf  third_party/highway/hwy/ops/arm_neon-inl.h:3090
0  XUL  jxl::N_NEON::GaborishStage::ProcessRow const  third_party/jpeg-xl/lib/jxl/render_pipeline/stage_gaborish.cc:71
1  XUL  jxl::LowMemoryRenderPipeline::RenderRect  third_party/jpeg-xl/lib/jxl/render_pipeline/low_memory_render_pipeline.cc:725
2  XUL  jxl::LowMemoryRenderPipeline::ProcessBuffers  third_party/jpeg-xl/lib/jxl/render_pipeline/low_memory_render_pipeline.cc:892
3  XUL  jxl::FrameDecoder::ProcessACGroup  third_party/jpeg-xl/lib/jxl/dec_frame.cc:547
4  XUL  jxl::FrameDecoder::ProcessSections const  third_party/jpeg-xl/lib/jxl/dec_frame.cc:700
4  XUL  jxl::ThreadPool::RunCallState<jxl::FrameDecoder::ProcessSections  third_party/jpeg-xl/lib/jxl/base/data_parallel.h:94
5  XUL  jpegxl::ThreadParallelRunner::RunRange  third_party/jpeg-xl/lib/threads/thread_parallel_runner_internal.cc:145
6  XUL  jpegxl::ThreadParallelRunner::ThreadFunc  third_party/jpeg-xl/lib/threads/thread_parallel_runner_internal.cc:175
7  XUL  std::__1::__invoke[abi:un170006]<void   /builds/worker/fetches/MacOSX14.4.sdk/usr/include/c++/v1/__type_traits/invoke.h:340

By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:

• First crash report: 2024-06-10
• Process type: Content
• Is startup crash: No
• Has user comments: No
• Is null crash: No

By analyzing the backtrace, the regression may have been introduced by a patch [1] to fix Bug 1900670.

[1] https://hg.mozilla.org/mozilla-central/rev?node=151cb0c06eea

:saschanaz, since you are the author of the potential regressor, could you please take a look?

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

:saschanaz, since you are the author of the regressor, bug 1900670, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Comment 2

[Andrew McCreight [:mccr8]]

ni? to gsvelto, as the demangling seems to be not working properly.

Comment 3

[Andrew McCreight [:mccr8]]

(In reply to Andrew McCreight [:mccr8] from comment #2)

ni? to gsvelto, as the demangling seems to be not working properly.

(Also in bug 1901750.)

Comment 4

[Timothy Nikkel (:tnikkel)]

jpeg xl is nightly only and presumably one has to enable the jpegxl pref for this too, so S3.

Comment 5

[Gabriele Svelto [:gsvelto]]

There's a lit of non-demangled symbols in these builds, did the compiler change recently? I've tried feeding these symbols to all the demanglers I know of and none demangles them properly; that suggests they may contain some new token that is not supported by demanglers yet or a bug in the compiler is causing it to generate invalid symbols (though I'd say the former is more likely).