-
-
Notifications
You must be signed in to change notification settings - Fork 21.1k
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
Crash in destructor AreaPair2DSW with Multi-Threaded physics #29369
Comments
I cannot reproduce it in latest version. |
I can still reproduce it, almost always crash in this project - |
I cannot reproduce this issue in the latest commit with that zip file on arch linux. I am, however, getting repeated messages in the debugger about a 'method/function failing' along with an eventual freeze of godot after about 20 seconds. Maybe a simpler example project would help highlight the issue? |
Do you check AAAAA.zip file from my latest post? |
With the newly uploaded zip, yes there is a crash |
I have narrowed down the issue with a more minimal project: area_2d_process_multithreaded.zip
The documentation suggests that any physics related stuff should be done in the |
It seems to crash in 3.2.4 beta4 when you duplicate the areas (in the newest project). Although I tried it on master and there's some crash that looks unrelated, so not sure. |
New minimal project(2 scenes 1 script) - AA.zip Looks that only changing position, monitoring or monitorable properties is enough to crash Godot.
|
Still crashes in 3.x (I tried AA.zip attached by @qarmin ). You don't even need to use
|
Does not crash in 4.0 RC 3; changing milestone to |
This also doesn't crash in 3.4 and later. It crashes in 3.3. |
Godot version:
3.2 a69436a
OS/device including version:
Ubuntu 19.04
Issue description:
When I run game, then it crash with this backtrace
Minimal reproduction project:
https://github.com/qarmin/The-worst-Godot-test-project
commit 8bfcc7a5af0957d8295589729b4379f233153603
Old
Bug.zip
New
AAAAAAAAAAAAAAAAAAAAAA.zip
The text was updated successfully, but these errors were encountered: