Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.68f1
6000.3.10f1
6000.4.0b10
6000.5.0a7
Issue ID
UUM-135651
Regression
No
Crash on CallWindowProcW when entering Play mode for the second time and running the Editor in the background while using System.Windows.Forms functions
How to reproduce:
1. Open the attached “IN-132970” project
2. Open the “GameScene“
3. Enter, then exit Play mode
4. Enter Play mode once again
5. Open any other program (for example Notepad or any IDE)
6. Observe the crash
Reproducible with: 6000.0.0b16, 6000.0.68f1, 6000.3.10f1, 6000.4.0b10, 6000.5.0a7
Could not test with: 6000.0.0b15 (couldn't solve errors from downgrading)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
First few lines of the stack trace:
0x00007FFC1AB56B46 (USER32) CallWindowProcW
0x00007FFC1AB563CC (USER32) SendMessageW
0x00007FFC1AB87FC3 (USER32) GetWindowDpiAwarenessContext
0x00007FFC1CDC5A74 (ntdll) KiUserCallbackDispatcher
0x00007FFC1A9112C4 (win32u) NtUserPeekMessage
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
Add comment