RSS FeedWe have a very active and passionate community and our forums is the place to get tips and chat with other users about all our products. Join today and meet some great people! Note: if you have a feature to request or a bug to report, make sure you use this contact form.
This topic has been marked 
resolved by our support staff or its poster.
T'hain Esh Kelch
Member
I often have Linkinus running for days at a time, and I see a problem whenever it has run in the background for a prolonged time in the background (Hours).
When you switch back to Linkinus, it locks up for 5-10 seconds. Also, when you then try to select other channels, this lock repeats until you've been through them all. I don't have logging activated, so that can't be it. It might be related to history, but I haven't verified this yet.
Okeanos
Moderator
What Style do you use? How large is your history? How many channels, connections and query windows do you have open?
T'hain Esh Kelch
Member
Style is whisper, history is 500. 7 servers with 16 channels open at all times. Most have little activity. I do not now what a query window is?
Okeanos
Moderator
A query window would be a private chat with another IRC user or other items (such as grouped notices) with the "person" icon.
miknight
Member
I experience this problem as well. I am connected to 2 servers and in a total of 10 channels, no query windows, 200 lines of history.
My delay is not quite as long as 5-10 seconds though, probably more like 2-3 seconds of unresponsiveness when the window gains focus. I leave my computer on with it connected, so Linkinus can be running for days or weeks without a restart.
miknight
Member
After running Linkinus for 15 days straight, the Linkinus process was using 2.2GB of resident memory and the Linkinus Agent process was using about 650MB of resident memory.
I think this might be related to the focus delay. After restarting it and rejoining all the servers/channels there was no longer a focus delay and the processes were using 347MB and 255MB of RSS respectively.
It seems like there is a memory leak of some kind, possibly relating to conversation history not being released. Please let me know if I can help further with debugging this.
miknight
Member
Another update: Quitting Linkinus (but leaving the agent running) and starting it again will make it responsive again.
Nicolas
Co-founder & Developer
Hey,
Thank you for posting. This is a bug that was happening to some users, and we fixed it. The fix will be available in the next update (Linkinus 2.2).
Reply
You must log in to post.