1871505 - Crash in [@ <unknown in nvwgf2umx.dll> | BaseThreadInitThunk]

Status: NEW

(Core :: Graphics, defect)

Description

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

Crash report: https://crash-stats.mozilla.org/report/index/561bb669-060c-47f3-861a-5a3bf0231216

Reason: EXCEPTION_ACCESS_VIOLATION_READ

Top 10 frames of crashing thread:

0  nvwgf2umx.dll  <unknown in nvwgf2umx.dll>  
1  nvwgf2umx.dll  <unknown in nvwgf2umx.dll>  
2  nvwgf2umx.dll  <unknown in nvwgf2umx.dll>  
3  nvwgf2umx.dll  <unknown in nvwgf2umx.dll>  
4  nvwgf2umx.dll  <unknown in nvwgf2umx.dll>  
5  nvwgf2umx.dll  <unknown in nvwgf2umx.dll>  
6  nvwgf2umx.dll  <unknown in nvwgf2umx.dll>  
7  nvwgf2umx.dll  <unknown in nvwgf2umx.dll>  
8  nvwgf2umx.dll  <unknown in nvwgf2umx.dll>  
9  kernel32.dll  BaseThreadInitThunk  

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

• First crash report: 2023-10-20
• Process type: GPU
• Is startup crash: No
• Has user comments: No
• Is null crash: Yes - 1 out of 26 crashes happened on null or near null memory address

Comment 1

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

The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Kelsey Gilbert [:jgilbert]]

Driver crash, volume not too bad, crashing entirely in a driver thread stack, so not that obviously actionable. I'm saying 'S3'.