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?
Comments (3)
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
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?