Skip to content
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

Possible allocator memory corruption? #105

Open
SUPERCILEX opened this issue Jan 30, 2022 · 1 comment
Open

Possible allocator memory corruption? #105

SUPERCILEX opened this issue Jan 30, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@SUPERCILEX
Copy link

Describe the Bug

Unfortunately, I'm not sure. Using wee_alloc causes bugs in Bevy, suggesting a bug somewhere in the allocator.

Steps to Reproduce

See bevyengine/bevy#3763

Expected Behavior

No memory corruption bugs.

Actual Behavior

Memory corruption.

@TomPridham
Copy link

TomPridham commented Mar 6, 2022

it also seems to never actually free any memory and will eventually oom even with the most basic bevy app.
Screenshot from 2022-03-05 23-13-36

#[global_allocator]
static ALLOC: wee_alloc::WeeAlloc = wee_alloc::WeeAlloc::INIT;

#[wasm_bindgen]
pub fn run() {
    App::new()
        .add_plugins(DefaultPlugins)
        .run();
}

using the default allocator works as expected
Screenshot from 2022-03-05 23-29-59

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants