Closed Bug 1782499 Opened 2 years ago Closed 1 year ago

Crash in [@ mozalloc_abort | abort | nv50_ir::NVC0LoweringPass::processSurfaceCoordsNVE4] on Fedora 36

Categories

(Core :: Graphics, defect)

x86_64
Linux
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: gsvelto, Unassigned)

References

()

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/0d819f53-b4b0-443c-9072-48aae0220801

MOZ_CRASH Reason: ```Redirecting call to abort() to mozalloc_abort


Top 4 frames of crashing thread:

0 firefox mozalloc_abort /usr/src/debug/firefox-102.0-1.fc36.x86_64/memory/mozalloc/mozalloc_abort.cpp:35
1 firefox abort /usr/src/debug/firefox-102.0-1.fc36.x86_64/memory/mozalloc/mozalloc_abort.cpp:88
2 libgallium_dri.so nv50_ir::NVC0LoweringPass::processSurfaceCoordsNVE4 [clone .cold] /usr/src/debug/mesa-22.1.4-2.fc36.x86_64/src/gallium/drivers/nouveau/codegen/nv50_ir_lowering_nvc0.cpp:2049
3 libgallium_dri.so tc_call_flush_resource /usr/src/debug/mesa-22.1.4-2.fc36.x86_64/src/gallium/auxiliary/util/u_threaded_context.c:3777

This isn't a crash in our code, it's a Fedora-specific crash in Mesa while playing videos on Linux. I'm filing it because it's fairly high volume given the very narrow user group it affects (running Fedora, using a dual-GPU laptops Intel IGP/NVidia discrete). All users are on Mesa 22.1.3 or 22.1.4 and the line of code that's causing the crash shouldn't trigger it in upstream Mesa, so I suspect a Fedora-specific regression.
Flags: needinfo?(stransky)
Summary: Crash in [@ mozalloc_abort | abort | nv50_ir::NVC0LoweringPass::processSurfaceCoordsNVE4] → Crash in [@ mozalloc_abort | abort | nv50_ir::NVC0LoweringPass::processSurfaceCoordsNVE4] on Fedora
Summary: Crash in [@ mozalloc_abort | abort | nv50_ir::NVC0LoweringPass::processSurfaceCoordsNVE4] on Fedora → Crash in [@ mozalloc_abort | abort | nv50_ir::NVC0LoweringPass::processSurfaceCoordsNVE4] on Fedora 36

Better to file Fedora bug then.

Flags: needinfo?(stransky)

Seems to have mostly gone away

Severity: S2 → S3

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.