Many thanks! As soon as I have fixed the stupid sbt build again, I'll have a look! On May 21, 2014 3:53 PM, "Brantley Hobbs" <[email protected]> wrote:
> Thank you Andreas! > > I have left a comment on your issue. I have Chrome javascript heap > snapshots spaced about 10 minutes apart if any developer wants them. The > topmost culprit for memory usage is the Rickshaw.Graph objects; they're > never being released and consuming huge amounts of RAM. It could be that > the container wrapping them is not being released though, so there's likely > nothing wrong with the graphs, per se. > > Devs: I will try to get you any data you need to troubleshoot this; it's > something I'm willing to invest time in. > > Brantley > > > On Tue, May 20, 2014 at 3:07 AM, Andreas Franz <[email protected]>wrote: > >> Hi, >> >> it's the same for me I tried everything Ubuntu, Lubuntu, Chrome OS, >> Windows and all combinations of browsers Internet Explorer, Chrome, >> Firefox. I opened an issue on GitHub ( >> https://github.com/Graylog2/graylog2-web-interface/issues/782) >> >> Regards, >> Andreas >> >> Am Freitag, 16. Mai 2014 14:16:54 UTC+2 schrieb Brantley Hobbs: >> >>> Hi all! >>> >>> We are using Graylog dashboards (a fantastic feature!) to drive large >>> TV's as datacenter displays. Problem is that every browser we've tried: >>> Chrome, Firefox, even IE, eventually consumes all available RAM and then >>> crashes. >>> >>> I've done some basic profiling on the pages, and from my admittedly >>> untrained eye it looks as though listeners aren't being garbage collected. >>> >>> On a related note, I and others have noticed that when a Graylog page >>> (be it a stream, dashboard, index list, what have you) loses focus, it >>> stops updating. When that happens, some of the RAM is released back to the >>> system (but not all). I now wonder if this is in place to prevent exactly >>> this issue of running out of RAM. I have submitted a feature request to the >>> team to allow page refreshes even when the window doesn't have focus. >>> >>> So, my question is two-fold: >>> 1. Has anyone found the right combination of browser/OS to successfully >>> keep the dashboards open for more than an hour or so unattended? >>> 2. Is there a way to have the page not refresh once per second? >>> Perhaps once every 5 seconds would be enough for the garbage collection in >>> the browser to run and release any unused objects' RAM back. >>> >>> Thanks! >>> Brantley Hobbs >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "graylog2" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "graylog2" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
