Open keithah opened 5 years ago
Thanks for reporting. I wonder if it's some kind of runaway leak that the app isn't clearing up on. Have you tried re-adding IRCCloud since removing it to see if it still eats resource like this? After launching the app, how long does it take to get into this state, i.e. after an hour, a day etc?
After launch it was happening pretty quickly. I'll add it again and test again though.
I just came back to my iMac this morning, and saw Wavebox at 20gb of ram usage. I couldn't bring up Prefs to look at Task Manager, but it was likely irc cloud. It's no longer instant, it does take a few hours. I have noticed poor performance in general with it when IRCCloud is enabled. I have deleted/reenabled again and will let you know if it happens again.
There was an issue we used to see a while ago, that was a result of a leak from alert and confirm prompts being active for quite some time. This kind of sounds like it could be related to that.
If it does happen again it would be handy to have a screenshot of the memory tab from the macOS activity monitor. Although it doesn't have all the info that the Wavebox one does, it might give some hints. E.g.
So I've been using the irccloud-desktop electron instance, while I haven't seen the memory leak, I've definitely had it hit 100% cpu numerous times and become laggy/unresponsive, so I think it's something they are doing, unfortunately. I'll try to work with them to nail down the issue with their own app and then I bet Wavebox will magically work again. :)
Expected & actual behavior IRCCloud becomes very laggy and almost unusable. I suspended it, still noticed issues, looked at task monitor and saw it was nearly 20% CPU and almost 6gb of ram. I have been running IRCCCloud in Wavebox for an entire year and have not had an issue. I had to remove it entirely for resources to be freed again and now my computer is much more usable.
Steps to reproduce I'm on 4 networks: efnet, bitlbee, freenode and irccloud. I first noticed it when linking twitter bitlbee, but disconnected that and still had issues.
Is the bug persistent or intermittent? always happen
Screenshots
Happy to test again, submit logs, etc. I've only noticed this issue on 4.10.1.