Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0a1
Issue ID
601046
Regression
Yes
Editor crashes every time I log in on my computer after it was locked
Regression from 5.0 alpha1.
- Import the attached project in any Unity version bigger than 5.0 alpha 2
- Open the AngryBots scene and press Play
- Lock your computer
- Log back in and try to focus the Editor
Instant crash:
Load scene 'Temp/__EditModeScene' time: 482.350128 ms
GPUProgram: loaded 1:5124736d0c3b812806b39a4f46e1b013 kwords 0000000000005020 from cache in 6.21 ms
GPUProgram: loaded 2:5def29178be4dbab9e732682a741b85e kwords 0000000000005020 from cache in 0.19 ms
HandleD3DDeviceLost
HandleD3DDeviceLost: still lost
HandleD3DDeviceLost
HandleD3DDeviceLost: still lost
HandleD3DDeviceLost
HandleD3DDeviceLost: still lost
HandleD3DDeviceLost
HandleD3DDeviceLost: still lost
HandleD3DDeviceLost
HandleD3DDeviceLost: needs reset, doing it
FullResetD3DDevice
ResetD3DDevice
dev->Reset
D3Dwindow device not lost anymore
D3D9: attempt to lock null vertex buffer
validateIndex == result
(Filename: C:/buildslave/unity/build/Runtime/GfxDevice/threaded/GfxDeviceWorker.cpp Line: 644)
Crash!!!
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment