-
Notifications
You must be signed in to change notification settings - Fork 12
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
Whiteboard Crashes after using it for 25+ minutes #258
Comments
same here! |
I have the exact same problem.
to my docker-compose.yaml but it's not really a fix... |
I have the same issue as well. |
I guess we should check and make sure that async getUserSocketsAndIds(roomID) {
const sockets = await this.io.in(roomID).fetchSockets()
return Promise.all(sockets.map(async (s) => {
const data = await this.socketDataManager.getSocketData(s.id)
return {
socketId: s.id,
user: data.user,
userId: data.user.id,
}
}))
} |
Thank you for reporting this issue! We've been able to reproduce the crash locally after extended usage. @TobiasHofmaenner's suggestion about adding empty checks for We'll investigate the cause and provide proper fixes in upcoming releases. Thank you! |
I used a whiteboard for about 25 Minutes and the server suddenly crashed. I had it open on 3 devices with the same Nextcloud account.
All changes were lost and nothing was saved to the Nextcloud (reopening it resulted in an empty file).
It was not possible to use the built-in download button to back up after the server crashed because closing the error alert stopped the whole "exalidraw" session and while the message was displayed it was not possible to interact with the page.
Logs:
The text was updated successfully, but these errors were encountered: