Forum Discussion
Hi ShadowPeak,
Thank you for this detailed post! I'm an engineering manager here at GoTo and we do look into post here in this community. I agree with your assessment: it does sound like the 4GB limit. This is a very good observation and the best we can hope for as a bug report. We are looking into issues like this and performance in general. Do you have an option to upload those dumps somewhere? They might be useful. We'll try to reproduce your observation in the meantime.
Can you tell us more details about the session? You wrote it has been running 7 hours+. Was that indeed GoToTraining? And which features did you use? Webcam, ScreenSharing, Breakout Rooms, Recording, Drawing Tools or Remote Keyboard and Mouse Control (Control Sharing)?
Yes my sessions run about 8 hours using GotoTraining. Only features used are me continuously sharing a screen and me on audio with occasional audio from about 8 attendees. No cams at all, no screen sharing/control from attendees, no breakout rooms, no recording. For drawing I only use the SysTools Zoomit suite but very intermittently. I was watching the renderer memory utilization yesterday and the leakage seems to slow down quite a bit when my screen is paused but still shared; by keeping the screen paused most of the day whenever possible I was able to get through the 8 hour session without running the renderer out of memory. Will look today and see if leakage still happens when no screen is shared.
Please contact me on my email address associated with this account and if you can provide some kind of dropbox or SCP server I can upload the dumps. Thanks!
- GoToMathias2 years agoGoTo Contributor
Thanks for these details! I'll note them down in a ticket but I do not yet know when we'll get to it.
- KateG2 years agoGoTo Moderator
ShadowPeak I sent you a PM with an email on where to send the data.
- GoToMathias2 years agoGoTo Contributor
Hi ShadowPeak ,
we are still looking into this issue but we have not yet been able to identify a root cause. In the meantime, it looks like the browser version of the app does not suffer from this issue. Maybe this could be a workaround for you. Please let us know if the leak does not occur for you in the browser, if you give it a try.
Regards,
-Mathias