You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The recordings are obviously stored in RAM until "downloaded" so perhaps the OS is killing the thread as a suspected memory leak, or it's starting to swap the memory out and that's causing an issue.
I can watch chrome's memory footprint grow as the recordings progress but the tab crashes long before the machine runs out of memory.
I'll add a video, please hold the line caller...
The text was updated successfully, but these errors were encountered:
For audio recording I've used cleanfeed.net a few times. The way they have implemented this in Chrome is a download button and whenever you press that during an active recording it will download the entire recording up to that point. That plus ample warnings in case you accidentally try to close the browser tab. Easier done for a few tens of audio megabytes though.
Testing on alpha.
Steps to reproduce:
Start a room in director view.
Add some cameras with &view
Hit record on the cameras.
Wait.
After some time the tab crashes with the error code: RESULT_CODE_UNINSTALL_USER_CANCEL
According to Dan Bulant on this thread: https://support.google.com/chrome/thread/41588693?hl=en
"This code is used when the process behind webpage is killed by OOM killer"
The recordings are obviously stored in RAM until "downloaded" so perhaps the OS is killing the thread as a suspected memory leak, or it's starting to swap the memory out and that's causing an issue.
I can watch chrome's memory footprint grow as the recordings progress but the tab crashes long before the machine runs out of memory.
I'll add a video, please hold the line caller...
The text was updated successfully, but these errors were encountered: