Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.2.X
1.3.0-pre.4 - Entities
7000.0.0a1
Issue ID
ECSB-1319
Regression
No
Crash on "CallWindowProcW" when an image is added to a SubScene through the file browser in Play mode
How to reproduce:
1. Open the “IN-83784_repro“ project
2. Open the “InGameScene“
3. Enter Play mode
4. Enable the “Canvas“ component in “Canvas_Main“ GameObject
5. In the Game view, select the “png“ button
6. In the file browser window, select IN-83784/Asstes/testingBG.png
7. Exit the Play mode
8. Open the “test.cs“ script and add a space
9. Save the script
Expected result: The Editor runs
Actual result: The Editor crashes
Reproducible with: 1.2.3 (2022.3.38f1), 1.2.4 (2022.3.46f1), 1.3.0-pre.4 (2022.3.46f1)
Reproducible on: Windows 10
Not reproducible on: No other environment tested
A few lines of the Stack Trace:
0x00007FF93CF7EF5C (USER32) CallWindowProcW
0x00007FF93CF7E8CC (USER32) DispatchMessageW
0x00007FF93CF910C3 (USER32) SendMessageTimeoutW
0x00007FF93EE913E4 (ntdll) KiUserCallbackDispatcher
Notes:
- Sometimes the Stack trace can be missing
- Sometimes it might take around 10 seconds for the Editor to crash
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
The crash is not related to the entities package or even Unity. If I am commenting the call to open the file dialog in the class ImageToTiles.ReadTexture(), there is no issue. It is most likely coming from the Windows API being used to open the dialog (https://learn.microsoft.com/en-us/dotnet/api/system.windows.forms.openfiledialog?view=windowsdesktop-9.0).
The stack trace of the crash is referring to some windows API.