Skip to content

Memory leaks in CI for 4.0.3-stable #298

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
Bromeon opened this issue Jun 5, 2023 · 1 comment
Closed

Memory leaks in CI for 4.0.3-stable #298

Bromeon opened this issue Jun 5, 2023 · 1 comment
Labels
bug c: ffi Low-level components and interaction with GDExtension API c: tooling CI, automation, tools

Comments

@Bromeon
Copy link
Member

Bromeon commented Jun 5, 2023

One CI job linux-memcheck-4.0.3 is currently failing with memory leaks, and has been commented out (note that the job was wrongly named).

This one runs the current gdext version (compiled against 4.0.3 API) with a Godot nightly (4.1-dev) binary.

I haven't managed to isolate the leaks yet, as they don't seem to follow a 1:1 per-use pattern. For example, calling Array::default() causes a leak, but calling it twice doesn't cause more leaks, despite the stack trace pointing to this allocation. I wonder if this is a systematic problem similar to the dlclose issue from #133.

@Bromeon Bromeon added bug c: tooling CI, automation, tools c: ffi Low-level components and interaction with GDExtension API labels Jun 5, 2023
@Bromeon
Copy link
Member Author

Bromeon commented Jun 13, 2023

This configuration (run 4.0.3 API under 4.1 runtime) is no longer supported by Godot, see #305 for details.

@Bromeon Bromeon closed this as not planned Won't fix, can't repro, duplicate, stale Jun 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug c: ffi Low-level components and interaction with GDExtension API c: tooling CI, automation, tools
Projects
None yet
Development

No branches or pull requests

1 participant