search

microsoft / D3D9On12

The Direct3D9-On-12 mapping layer
MIT License
346 stars 37 forks source link

pls help crashed on intel uhd 770,windows 10, probably memory leak #31

Open luyt86 opened 2 years ago

luyt86 commented 2 years ago

Our game player reported one crash on intel uhd 770, windows10, our game is based d3d9 , Game engine error log has printed "ENGINE_INIT:RenderAPI Error:Context::DrawIndexed :hr = 80004005, primitive=0, base index=0, vertex count=20, start index=0, primitive count=10", and found stack crash on d3d9on12.dll, After profile the client, I find it probably exsist memory leak in d3d9on12, I also try use d3d dynamic vertex buffer and index buf with discard flag to draw dynamic vertex, still found memory grow in each frame lock buffer. wpa1 lockleak ,

dpieve commented 1 year ago

Hello. I have the same issue. Did you find a work around or do you know if it was fixed?

luyt86 commented 1 year ago

Hello, it seems that the official has not fixed this issue yet. I downloaded the source code myself and changed the memory allocation strategy to only use a fixed block of memory, which basically solved the problem of memory leaks. the fix code like this:[image: image.png]

dpieve @.***> 于2023年4月28日周五 01:12写道：

Hello. I have the same issue. Did you find a work around or do you know if it was fixed?

— Reply to this email directly, view it on GitHub https://github.com/microsoft/D3D9On12/issues/31#issuecomment-1526052971, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACXMUGIDDRC4GEMQJEI4ZDDXDKSJHANCNFSM5SUUWVDQ . You are receiving this because you authored the thread.Message ID: @.***>

luyt86 commented 1 year ago

[image: image.png]

Yutao Lu @.***> 于2023年5月10日周三 15:44写道：

Hello, it seems that the official has not fixed this issue yet. I downloaded the source code myself and changed the memory allocation strategy to only use a fixed block of memory, which basically solved the problem of memory leaks. the fix code like this:[image: image.png]

dpieve @.***> 于2023年4月28日周五 01:12写道：

Hello. I have the same issue. Did you find a work around or do you know if it was fixed?

— Reply to this email directly, view it on GitHub https://github.com/microsoft/D3D9On12/issues/31#issuecomment-1526052971, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACXMUGIDDRC4GEMQJEI4ZDDXDKSJHANCNFSM5SUUWVDQ . You are receiving this because you authored the thread.Message ID: @.***>

dpieve commented 1 year ago

@luyt86 Would it be possible for you to share the updated code with me?

Unfortunately, I am unable to reproduce the issue on my computer since I don't have a 12th generation Intel processor. As a result, I'm unable to thoroughly investigate the root cause of the issue.

If you could provide me with the updated code, I would be happy to make the necessary changes and build the DLLs to attempt to resolve the issue.

Your assistance would be greatly appreciated.