When I don't have cutegram hidden in the tray, it has about 20% cpu usage, and when hidden it's almost nothing. I'm running manjaro linux with i3 wm.
I ran it in verbose mode, and it kept outputing the following, over and over again every few seconds until I hid it in the tray, then it stopped
connection # 25 received rpc answer with 792 content bytes by session "fca18650b7867024" tg.core.session: processRpcMessage(), len= 792 tg.core.session: received message id "58e71085a9888c01" tg.core.session: rpcExecuteAnswer(), op = "fffffffff35c6d01" tg.core.session: workRpcResult: msgId = "58e71085a9888c01" tg.core.session: result for query "58e7108500000000" tg.core.session: unzipped data tg.core.session: acked query with msgId "58e7108500000000" ,pendingQueries: 2
I usually just leave it opened to the main group chat I use, if that makes a difference
When I don't have cutegram hidden in the tray, it has about 20% cpu usage, and when hidden it's almost nothing. I'm running manjaro linux with i3 wm.
I ran it in verbose mode, and it kept outputing the following, over and over again every few seconds until I hid it in the tray, then it stopped
connection # 25 received rpc answer with 792 content bytes by session "fca18650b7867024" tg.core.session: processRpcMessage(), len= 792 tg.core.session: received message id "58e71085a9888c01" tg.core.session: rpcExecuteAnswer(), op = "fffffffff35c6d01" tg.core.session: workRpcResult: msgId = "58e71085a9888c01" tg.core.session: result for query "58e7108500000000" tg.core.session: unzipped data tg.core.session: acked query with msgId "58e7108500000000" ,pendingQueries: 2I usually just leave it opened to the main group chat I use, if that makes a difference