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

Brush dies with Killed #103

Open
poly2it opened this issue Feb 5, 2025 · 2 comments
Open

Brush dies with Killed #103

poly2it opened this issue Feb 5, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@poly2it
Copy link

poly2it commented Feb 5, 2025

After some time, the latest version (f72f518) of Brush dies with Killed:

$ RUST_BACKTRACE=1 brush_app
Killed

There seem to also be some internal sufferings:

$ brush_app
thread 'tokio-runtime-worker' panicked at /build/cargo-vendor-dir/burn-jit-0.17.0/src/kernel/conv/conv2d/im2col.rs:218:10:
Image too large to run even one batch at once
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'tokio-runtime-worker' panicked at /build/cargo-vendor-dir/burn-jit-0.17.0/src/kernel/conv/conv2d/col2im.rs:65:10:
Image too large to run even one batch at once
Killed

However, those don't kill the app instantly.

Linux (NixOS) with an NVIDIA 3060.

@poly2it poly2it changed the title Brush dies with *Killed* Brush dies with Killed Feb 5, 2025
@poly2it
Copy link
Author

poly2it commented Feb 5, 2025

I can reproduce this on 0.2.0.

@poly2it
Copy link
Author

poly2it commented Feb 5, 2025

The error is not present on ca1caf7.

@ArthurBrussee ArthurBrussee added the bug Something isn't working label Mar 27, 2025
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