Closed Bug 1893354 Opened 11 months ago Closed 4 months ago

Crash in [@ igd10iumd64.dll | std::vector<T>::_Change_array]

Categories

(Core :: Graphics, defect)

Product:
Core
Component:
Graphics
Platform:
Other
Windows 10
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox127 --- affected

People

(Reporter: release-mgmt-account-bot, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/f30fbf59-efaa-4af6-bf2f-717f40240419

Reason: EXCEPTION_ACCESS_VIOLATION_WRITE

Top 10 frames of crashing thread:

0  igd10iumd64.dll  igd10iumd64.dll@0x1aa61  
1  igd10iumd64.dll  igd10iumd64.dll@0x20a6d3  
2  libGLESv2.dll  std::vector<angle::FormatID, std::allocator<angle::FormatID> >::_Change_array  /builds/worker/fetches/vs/VC/Tools/MSVC/14.39.33519/include/vector:2034
2  libGLESv2.dll  std::vector<angle::FormatID, std::allocator<angle::FormatID> >::_Resize_reallocate  /builds/worker/fetches/vs/VC/Tools/MSVC/14.39.33519/include/vector:1545
2  libGLESv2.dll  std::vector<angle::FormatID, std::allocator<angle::FormatID> >::_Resize  /builds/worker/fetches/vs/VC/Tools/MSVC/14.39.33519/include/vector:1568
2  libGLESv2.dll  std::vector<angle::FormatID, std::allocator<angle::FormatID> >::resize  /builds/worker/fetches/vs/VC/Tools/MSVC/14.39.33519/include/vector:1595
2  libGLESv2.dll  rx::ProgramD3D::updateCachedInputLayout  gfx/angle/checkout/src/libANGLE/renderer/d3d/ProgramD3D.cpp:3164
3  libGLESv2.dll  rx::StateManager11::setVertexShader  gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp:2447
3  libGLESv2.dll  rx::StateManager11::setDrawShaders  gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp:2435
3  libGLESv2.dll  rx::StateManager11::syncProgram  gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp:3001

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

  • First crash report: 2024-04-19
  • Process type: GPU
  • Is startup crash: No
  • Has user comments: No
  • Is null crash: Yes - 1 out of 3 crashes happened on null or near null memory address

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.

Component: General → Graphics
Severity: -- → S3

Closing because no crashes reported for 12 weeks.

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