Will try to diagnose this later, just wanted to get the report out, I have 3 services enabled, whatsapp, fb messenger and hangouts

Rambox: v0.X.X
OS: XXXX
Arch: x64 or ia32
It's the Hangouts tab, as soon as I enable hangouts, the memory goes off the roof
Also experiencing this. Can confirm - hangouts tab is the cause. Verified in both 64 and 32 bit versions.
I'm seeing what sounds like the same behaviour but in a Gmail tab. Version 0.5.8 on (Arch) Linux x64.
I'm seeing a Rambox process gradually increasing memory usage, for periods it seems to use 100% of a processor core, but at other times seems normal. Removing Gmail service ends the behaviour.
I see this too on Mac (Sierra). Gmail won't even load. Already tried to create a new service but getting the same result.
Seems to be the same as #863
I can confirm the bug. If I don't have GMail or Hangouts enabled but Whatsapp, Slack, Skype I don't have any problems - but once I add GMail and login, rambox eats all my RAM.
I did a memory snapshot - (heap+allocation profile&timeline). You can download it here (loadable in "memory" tab of devtools): https://s.jbbr.net/f/4797f350e7/?dl=1
Screenshots from devtool:


Same here, I installed rambox in a new laptop and suddenly the amount of ram the process takes, goes to the roof.
Anyone know how to get the previous version? I'm not finding an archived version list on the rambox.pro site.
@JamesValero https://github.com/saenzramiro/rambox/releases
i am seeing this too. my rambox install was using more then 6 gb of ram.
I am also experiencing this using Facebook Messenger. Whereas, Whatsapp of Slack are using less than 100 MB of RAM, Messenger is using around 1.5 GB even when it's running in the background (on Ubuntu Gnome).
I would recommend downgrade to the previous version until this is fixed.
Dunno when it will be.
Yes, this will be fixed in next release. Sorry guys.
The problem was caused because the javascript injection to get unread counter for Gmail and Hangouts.
New version will be released July 1st. ;)
I hope you mean "June 1st". Otherwise i would suggest to push a hotfix release asp cause gmail and hangouts are way to important to let them stay like this for over a month.
@sxe it is released already...check the releases on github
hehe ok, thx for the heads up, works fine for me.
Sorry, I don't get it,
Why close an issue if it is not fixed? keep it open for proper tracking
There was another issue with the same error.
Have you checked version 0.5.9 yet?
It seems to be working just fine now.
Seems like now there is an annoying popup display for hangouts notifications when you receive a new message, popping up several notification windows until you read the message.
I didn't even reported or noticed the issue, this is a purely development process question.
Based on the answer that the defect will be fixed in July i.e. next version (greater than 0.5.9), I understand that this has not been fixed yet (I haven't found a matching commit for it). If all of the above is true, I think the proper time to close an issue is on verification that indeed the issue was fixed.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.