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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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?