Opened 2 years ago
Closed 2 years ago
#9774 closed defect (fixed)
Crashed in Windows 11 build 10.0.22000.652 build
| Reported by: | 黄振波 | Owned by: | |
|---|---|---|---|
| Priority: | important | Component: | avutil |
| Version: | Keywords: | crash | |
| Cc: | Blocked By: | ||
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description (last modified by )
Summary of the bug:
A crashed happend in Windows 11 10.0.22000.652 build.
reprodue-able 100%
How to reproduce:
When i call av_hwframe_transfer_data to transfer GPU data to CPU data,
the crashe happend, while it worked fine before Windows 11 10.0.22000.652.
Here is the dump file: https://1drv.ms/u/s!AqL91iUT-5JUgSTtlMoP4Sbybo0U?e=zE6y0P
Unhandled exception at 0x00007FFFC8E4D9DF (d3d9on12.dll) in ReadyFor.exe.19472.dmp: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF. d3d9on12.dll!00007fffc8e4d9df() d3d9on12.dll!00007fffc8e4d025() d3d9on12.dll!00007fffc8e41a36() d3d9on12.dll!00007fffc8e41b7a() d3d9on12.dll!00007fffc8e413a9() d3d9on12.dll!00007fffc8e0f837() d3d9on12.dll!00007fffc8e0f44c() d3d9.dll!00007fffc9106cbc() d3d9.dll!00007fffc90130d7() d3d9.dll!00007fffc902e2ab() d3d9.dll!00007fffc90a382b() avutil-57.dll!00007fffb6d4cfd8() avutil-57.dll!00007fffb6d4d184() avutil-57.dll!00007fffb6d48163() avutil-57.dll!00007fffb6d481e7()
Change History (8)
comment:1 by , 2 years ago
| Status: | new → open |
|---|
comment:2 by , 2 years ago
| Component: | undetermined → avutil |
|---|---|
| Priority: | normal → important |
| Summary: | Crashed in Windows 10.0.22000.652 build → Crashed in Windows 11 build 10.0.22000.652 build |
| Version: | unspecified |
comment:3 by , 2 years ago
| Description: | modified (diff) |
|---|
comment:4 by , 2 years ago
| Description: | modified (diff) |
|---|---|
| Priority: | important → critical |
comment:5 by , 2 years ago
| Keywords: | crash added |
|---|---|
| Priority: | critical → important |
follow-up: 7 comment:6 by , 2 years ago
How high is the chance the use of API is wrong? Again, d3d9on12? Really? I though there is only 11on12.
Also where is the code?
comment:7 by , 2 years ago
Replying to Balling:
How high is the chance the use of API is wrong? Again, d3d9on12? Really? I though there is only 11on12.
Also where is the code?
It's reprodue-able 100% in Windows 11 10.0.22000.652 build.
Yes, d3d9on12, you can find it in C:\Windows\System32.
Here is the d3d9on12 codes: https://github.com/microsoft/D3D9On12.
About the code, I need to sort it out and try to submit it tomorrow.
comment:8 by , 2 years ago
| Resolution: | → fixed |
|---|---|
| Status: | open → closed |
Hi all:
I found this issuce should be d3d9on12.dll's bug.
I try to reproduce this issue today, but found it is unable reproduce,
and i found windows update the d3d9on12.dll to 10.0.22000.653.
It should be a update in KB5013943 (OS Build 22000.675): https://support.microsoft.com/en-gb/topic/may-10-2022-kb5013943-os-build-22000-675-14aa767a-aa87-414e-8491-b6e845541755
So i will close this CR, since it has been fixed in Windows release.
Thank you to all of you.
Try to reproduce with vanilla ffmpeg...