Closed Bug 622962 Opened 15 years ago Closed 15 years ago

Crash [@ mozilla::layers::ImageLayerD3D10::RenderLayer ] [@ atidxx32.dll@0xfbfa ][@ atidxx32.dll@0xfb5a ][@ atidxx32.dll@0x9269 ][@ atidxx32.dll@0x929e ][@ atidxx32.dll@0xe84f ][@ atidxx32.dll@0x3a6cb ][@ atidxx32.dll@0xe6bf ][@ atidxx32.dll@0x3b28b ]

Categories

(Core :: Graphics, defect)

x86
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 612103
Tracking Status
blocking2.0 --- final+

People

(Reporter: scoobidiver, Assigned: bas.schouten)

References

Details

(Keywords: crash, regression, Whiteboard: [softblocker])

Crash Data

It is a bug similar to bug 612103 but for ATI graphic cards. There are 1350 crashes/week in 4.0b8. Combined signatures are #8 top crasher in 4.0b8 for the last week. Signature atidxx32.dll@0xfbfa UUID 188bdac4-992e-4006-b83e-ae3ba2110104 Time 2011-01-04 13:01:53.384074 Uptime 9971 Install Age 29705 seconds (8.3 hours) since version was first installed. Product Firefox Version 4.0b8 Build ID 20101214170338 Branch 2.0 OS Windows NT OS Version 6.1.7600 CPU x86 CPU Info GenuineIntel family 6 model 26 stepping 5 Crash Reason EXCEPTION_ACCESS_VIOLATION_READ Crash Address 0x4 App Notes AdapterVendorID: 1002, AdapterDeviceID: 6898 Frame Module Signature [Expand] Source 0 atidxx32.dll atidxx32.dll@0xfbfa 1 atidxx32.dll atidxx32.dll@0xe837 2 atidxx32.dll atidxx32.dll@0x11911 3 atiuxpag.dll atiuxpag.dll@0x22e1 4 d3d10_1core.dll d3d10_1core.dll@0x2a280 5 d3d10_1core.dll d3d10_1core.dll@0x30ca5 6 d3d10_1.dll d3d10_1.dll@0x1b927 7 d3d10_1.dll d3d10_1.dll@0x228f3 8 d3d10_1.dll d3d10_1.dll@0x1baa0 9 d3d10_1core.dll d3d10_1core.dll@0x1cd99 10 d3d10_1.dll d3d10_1.dll@0x19987 11 xul.dll mozilla::layers::ImageLayerD3D10::RenderLayer gfx/layers/d3d10/ImageLayerD3D10.cpp:209 12 xul.dll mozilla::layers::ContainerLayerD3D10::RenderLayer gfx/layers/d3d10/ContainerLayerD3D10.cpp:263 Here are 4.0b8 reports: http://crash-stats.mozilla.com/query/query?product=Firefox&version=Firefox%3A4.0b8&platform=windows&branch=2.0&range_value=1&range_unit=weeks&query_search=signature&query_type=startswith&query=atidxx32.dll&build_id=&process_type=any&hang_type=any&do_query=1
blocking2.0: --- → ?
Keywords: regression
Indeed this is presumably the same bug, which I still haven't been able to catch in a debug build, once we do, it will probably be trivial to debug.
Assignee: nobody → bas.schouten
blocking2.0: ? → final+
Whiteboard: [soft blocker]
Whiteboard: [soft blocker] → [softblocker]
Seems fixed by fixing Bug 612103.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Resolution: FIXED → DUPLICATE
One crash happened after the fixing of bug 612103. Is the additional patch (Only do a warning in the case of failure) going to fix that? bp-a928bcae-a295-4624-8c4b-7174a2110115 Frame Module Signature [Expand] Source 0 atidxx32.dll atidxx32.dll@0x1fac62 1 atidxx32.dll atidxx32.dll@0x214e74 2 atidxx32.dll atidxx32.dll@0xb204 3 atidxx32.dll atidxx32.dll@0x10e5c 4 atiuxpag.dll atiuxpag.dll@0x2118 5 d3d10_1core.dll NMultithread::CDevice::Draw 6 xul.dll mozilla::layers::ThebesLayerD3D10::RenderLayer gfx/layers/d3d10/ThebesLayerD3D10.cpp:194 7 xul.dll mozilla::layers::ContainerLayerD3D10::RenderLayer gfx/layers/d3d10/ContainerLayerD3D10.cpp:288 8 xul.dll mozilla::layers::LayerManagerD3D10::Render gfx/layers/d3d10/LayerManagerD3D10.cpp:518 9 xul.dll mozilla::layers::LayerManagerD3D10::EndTransaction gfx/layers/d3d10/LayerManagerD3D10.cpp:285 10 xul.dll nsDisplayList::PaintForFrame layout/base/nsDisplayList.cpp:506 11 xul.dll nsLayoutUtils::PaintFrame layout/base/nsLayoutUtils.cpp:1460 12 xul.dll PresShell::Paint layout/base/nsPresShell.cpp:6112
Nope, this is also in ThebesLayer, probably a completely different problem.
I filed bug 626238 for the issue in comment 3.
Crash Signature: [@ mozilla::layers::ImageLayerD3D10::RenderLayer ] [@ atidxx32.dll@0xfbfa ] [@ atidxx32.dll@0xfb5a ] [@ atidxx32.dll@0x9269 ] [@ atidxx32.dll@0x929e ] [@ atidxx32.dll@0xe84f ] [@ atidxx32.dll@0x3a6cb ] [@ atidxx32.dll@0xe6bf ] [@ atidxx32.dll@0x3b28b ]
You need to log in before you can comment on or make changes to this bug.