-
Notifications
You must be signed in to change notification settings - Fork 1
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
OOM error not shown during tracks preprocessing #51
Comments
The same with opening lots of BED files:
|
I can confirm that this can (and does) happen. |
Since JBR remains fully functional after this happens, we should try to show some feedback to user except errors in logs. |
@olegs I agree fully. We can try to catch the OOM and report it as a processing error. |
TODO:
|
There's a problem here: memory isn't freed in this scenario, so now the browser and its components won't have enough memory to function normally. We could instruct the track to release its data or replace the failed track with a dummy one. |
I've tried to open data set on ATAC-Seq
/mnt/stripe/bio/raw-data/geo-samples/PRJNA392905/
- all the span models simultaneously, and JBR didn't open them without any error messages.The text was updated successfully, but these errors were encountered: