-
-
Notifications
You must be signed in to change notification settings - Fork 21.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editing Tileset Causes Crash to desktop #63534
Comments
I'm able to trigger crash by randomly clicking things, but didn't get any stack trace. Might be related to disabling layers, I think I once triggered it during normal use. |
After messing with it some more, it seems to be something to do with the update process of the tile set properties. If I add a physics layer for instance that regularly triggers the crash as well. But not every time, its intermittent. I can follow the same process 3 times and each time it crashes but at different steps. If I leave the scene open for a long time and do not edit the tile set, its fine, no crash. Something handling changes common to all the tileset properties is probably the culprit. |
I think I have a related bug. I created a new tileset and dropped my art in which was a large spritesheet. The system auto-detected the tiles at 16x16 and as soon as I clicked to change it to 32x32 I got a crash. But yes, changing the tileset properties crashed me. This was on Win10 64. |
Getting a consistant crash when setting TileSet to a TileMap. Steps:
|
^ same crash as in #67049 |
The call stack that I get from a similar crash :
|
I cannot reproduce the bug. @winter5un could you confirm it is still here in the latest beta? |
To hazard a guess, it's probably all related to the fact that the TilesetEditor runs on its own thread. It might need a broader evaluation of thread safety, but my potential suggested fix for this might be connecting signal with the deferred flag. The tileset editor seems to have other warnings about parenting nodes too. |
I don't think it does. I did not implemented that and, as far as I am aware, I don't think editors run outside the main thread. Edit: I realized the TileSetEditor has indeed a thread, but it's only used to generate the thumbnails of the tilemap patterns. So well, yeah, hte problem might be here, as #72020 seems to suggest. |
Can you still reproduce this in 4.0.3 and 4.1-beta3 or later? |
It also happens in macOS Macbook Pro M1 Trace:
|
To reproduce: open Specificaly
Exception: EXC_BAD_ACCESS (code=1, address=0x0)
It appears |
Can someone confirm this on latest? Should be fixed by: |
It seems this issue included multiple reports of possible different crashes, but not a lot of clear reproduction projects. I tested the MRP from the OP: #63534 (comment) I tested the MRP from #63534 (comment) but it seems to be a different bug that was already fixed. Apparently duplicate of #67049. And finally @ShlomiRex's report in #63534 (comment) is not related to TileSet at all, but to a big log file causing a crash in the script editor. Indeed |
Godot version
4.0-alpha12
Edit: and 4.0-alpha14
System information
Ubuntu 21.10 (screenshot with more info attached)
Issue description
Same as Title
Steps to reproduce
Attached is a minimal project which includes to log files and a short video showing how to reproduce. In the end of the video the editor becomes non-responsive followed by a long crash (edited out the crash as it took forever but the log is there)
Added a layer and messed with the names of the layers then it crashed. Might or might not be related to that..........
Steps:
Minimal reproduction project
tile_set_4.0a12_repro.zip
The text was updated successfully, but these errors were encountered: