-
-
Notifications
You must be signed in to change notification settings - Fork 98
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 - white screen and exception when stopping recording #58
Comments
Closing and reopening Edge freed the memory and I can use gifcap again |
Unsure of what we could do here. Should we have a soft limit on the memory? Is there anyway I can figure out we're getting close to OOM? An event on OOM would be too late. Also, reloading don't work I'm guessing cause they reuse the same engine/scope. |
Any idea why the memory wasn't getting freed? At the least you should catch |
Well, 5 minutes of recording. That's a lot of memory. I'm guessing it hit OOM and then just hangs in there. I'm guessing OOM errors could surface from all over the place, so wrapping around |
I mean if we can't free the memory, a message on screen would be better than needing to dig through devtools. |
What about something like this during recording?
If the memory error is caught during recording, it is unlikely to occur again during trimming/cropping unless the user has other memory changes on their system. Those changes are outside of the application's control though and I am not sure if they should try to be accounted for. |
This was on a gif that I tried to record after accidentally leaving it recording for 5 minutes. Reloading/closing+reopening the tab doesn't fix the problem.
The text was updated successfully, but these errors were encountered: