We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Unfortunately, I'm not sure. Using wee_alloc causes bugs in Bevy, suggesting a bug somewhere in the allocator.
See bevyengine/bevy#3763
No memory corruption bugs.
Memory corruption.
The text was updated successfully, but these errors were encountered:
it also seems to never actually free any memory and will eventually oom even with the most basic bevy app.
#[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
Sorry, something went wrong.
Remove suggestion to use weealloc, as it seems broken with Bevy
8b9ffd5
See rustwasm/wee_alloc#105 Closes #129
wee_alloc
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: