Skip to content

Crash on exit in release exports with call stack tracking enabled in project settings #106667

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

Closed
limbonaut opened this issue May 21, 2025 · 0 comments · Fixed by #106691
Closed

Comments

@limbonaut
Copy link
Contributor

limbonaut commented May 21, 2025

Tested versions

  • Reproducible in 4.5-dev [be3ecae]

System information

Arch Linux on Wayland - Wayland display driver, Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 Laptop GPU - 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 threads)

Issue description

I discovered this issue while working on Godot 4.5 support in sentry-godot GDExtension.

When callstack tracking is enabled in release exports via debug/settings/gdscript/always_track_call_stacks, exported builds can crash on exit. With a GCC build on Linux (target=template_release debug_symbols=yes), I get SIGABRT and this printed:

double free or corruption (!prev)

Callstack state:

Image

Likely related to:

Steps to reproduce

Enable debug/settings/gdscript/always_track_call_stacks in the project settings. I wasn't able to reproduce it on an empty project. You can try with a sample or a production project. It crashed with several different projects, but not with a minimal setup, for some reason. This also happens on macOS. Didn't test on Windows.

Minimal reproduction project (MRP)

Don't have one at the moment. I'll see if I can reproduce in some public demo project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants