Search Issue Tracker
Fixed in 4.5.4
Votes
0
Found in
4.5.3f3
Issue ID
627566
Regression
No
coming back to computer after windows screensaver was on,
coming back to computer after windows screensaver was on, gives this error message:
allocation 0x00000000 already registered (at) C:/BuildAgent/work/d63dfc6385190b60/Runtime/GfxDevice/d3d/D3D9Utils.cpp:l167 size 0; now calling from C:/BuildAgent/work/d63dfc6385190b60/Runtime/GfxDevice/d3d/D3D9Utils.cpp:l167 size 0?
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Chloeman
Mar 18, 2020 14:35
information here was very useful for me as it allowed me to fix my issue pretty easily. Someone like https://www.intensedebate.com/people/mario888 were criticized for not thinking of their customers. Now they are keen to help them anyhow
WalterEspinar
Jan 29, 2015 17:36
same here
allocation 0x00000000 already registered @ C:/BuildAgent/work/d63dfc6385190b60/Runtime/GfxDevice/d3d/D3D9Utils.cpp:l167 size 0; now calling from C:/BuildAgent/work/d63dfc6385190b60/Runtime/GfxDevice/d3d/D3D9Utils.cpp:l167 size 0?
StevenDuwa
Jan 06, 2015 13:27
I have the same issue after coming back from screensaver.
Unity version : 4.6.0b17
allocation 0x00000000 already registered @ C:/BuildAgent/work/d63dfc6385190b60/Runtime/GfxDevice/d3d/D3D9Utils.cpp:l167 size 0; now calling from C:/BuildAgent/work/d63dfc6385190b60/Runtime/GfxDevice/d3d/D3D9Utils.cpp:l167 size 0?