MacOS crash with backtrace when toggling node visibility

[Koyper]

Godot version

3.5.rc2

System information

MacOS 12.2 M1

Issue description

Happened once also in 3.5.rc1 - See #61199

Project crash while running after toggling node visibility in editor.

 handle_crash: Program crashed with signal 11
 Engine version: Godot Engine v3.5.rc.custom_build
 Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
 [1] 1   libsystem_platform.dylib            0x00000001913144e4 _sigtramp + 56
 [2] GDScriptFunction::call(GDScriptInstance*, Variant const**, int, Variant::CallError&, GDScriptFunction::CallState*) (in Godot) (gdscript_function.cpp:0)
 [3] Object::call(StringName const&, Variant const**, int, Variant::CallError&) (in Godot) (object.cpp:899)
 [4] _Thread::_start_func(void*) (in Godot) (core_bind.cpp:2715)
 [5] Thread::callback(Thread*, Thread::Settings const&, void (*)(void*), void*) (in Godot) (thread.cpp:79)
 [6] void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (*)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*, Thread::Settings, void (*)(void*), void*> >(void*) (in Godot) (thread:299)
 [7] 7   libsystem_pthread.dylib             0x00000001912fd240 _pthread_start + 148

Steps to reproduce

Not able to reproduce

Minimal reproduction project

No response

[Calinou]

PS: Code blocks should use triple backticks like this (with an optional language name for syntax highlighting):

```gdscript
code here
```

I edited your post accordingly, but remember to do this in the future 🙂

[Koyper]

Will do - thanks...

[akien-mga]

We would need more details to be able to solve this, currently there are no indications on how the bug can be reproduced. I understand you might not have been able to reproduce it so the bug is likely still valid, but just mentioning the current state to make expectations clear.

[Koyper]

The crash happens when the project is playing and I make some modification to a function, such as adding a variable or changing a value. It seems like only one or two such changes can trigger the crash. It happens on both arm64 and x86 osx binaries. I will try to pay more attention to exactly what I did the next time it happens and see if I can repeat it. Up until now it has seemed random, being caused by different modifications. The project is completely stable when exported and when no changes while playing have been made in the editor, and typically when I’m making a lot of changes while playing. It happens maybe once over approximately four hours of editing (totally subjective estimate). Thanks!

…

On Jun 10, 2022, at 7:21 AM, Rémi Verschelde ***@***.***> wrote: We would need more details to be able to solve this, currently there are no indications on how the bug can be reproduced. I understand you might not have been able to reproduce it so the bug is likely still valid, but just mentioning the current state to make expectations clear. — Reply to this email directly, view it on GitHub <#61469 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIDFM5G3S5PTHROB7ZOJE3TVOMXLFANCNFSM5XELJJHQ>. You are receiving this because you authored the thread.

[Koyper]

To clarify…the crash rarely happens even when I am making numerous changes in the editor while the project is playing...

…

On Jun 10, 2022, at 7:21 AM, Rémi Verschelde ***@***.***> wrote: We would need more details to be able to solve this, currently there are no indications on how the bug can be reproduced. I understand you might not have been able to reproduce it so the bug is likely still valid, but just mentioning the current state to make expectations clear. — Reply to this email directly, view it on GitHub <#61469 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIDFM5G3S5PTHROB7ZOJE3TVOMXLFANCNFSM5XELJJHQ>. You are receiving this because you authored the thread.