Artur Hefczyc opened 4 years ago
|
|
Possibly dup of #issue #332? Had the same issue yesterday and after a couple of restarts and hours passed it started working just fine. I suggested that it may be related to the flood of messages (I had a couple of groups with hundreds of unread messages) and @andrzej.wojcik said it was a possibility. |
|
After restart it works just fine. It seems that after some time it just hangs. And I do not have a flood of messages overnight. |
|
@kobit In case of hangs, please use |
|
It happened to me today, please find probe from the process attached. |
|
Thank you for this process probe. It pinpoints the cause of the issue to unread message state (loading messages and updating its state). I'll work on that and provide a fix in the next build. |
|
Actually, "unread" state is not causing this issue. After deeper analysis, it looks like "scanning for links" to generate previews for messages is causing this issue. |
|
I've applied a possible fix (one that was suggested from the probe attached by @wojtek). Please upgrade BeagleIM, a new build is available via HomeBrew, and let me know if that solved the issue. |
|
I checked the latest build and it seems to be snappier. I'll keep an eye on it and report if anything happens. |
|
After the weekend the BeagleIM was still responsive and snappy after receiving hundreds of messages. |
|
Mine was dead in the morning. I mean, crashed, non-existen, null ;-) But this is better than hanging and pretending to work. And there is no window or notification offering to send crash report or anything like this. Anyway, I guess, this ticket can be closed and resolved. |
|
The crashing issue is "known" to me (I'm aware of it), but I do not have a solution yet. It looks like an internal exception within networking code from Apple which is used by us. I have an idea for a fix (which would improve connection reliability in Siskin) but it is just an idea and not an easy one so I need to experiment with this fix for a while. |
|
@kobit Do you still have this issue? or this one is solved? |
|
Updated to BeagleIM.5.0-b130, started and the client crashed within 1h. |
|
@kobit Could you attach the crash log? Without it, I cannot do almost anything. There were issues with b129 and I hoped that b130 fixed them. |
|
Sure, here is it:
|
Type |
Bug
|
Priority |
Normal
|
Assignee | |
Version |
5.0
|
Spent time |
8h 30m
|
Version 5.0 (113)
This built hang just right after first start after upgrade. Today, in the morning seemed to run but it was unresponsive. I had to force quit it. After start it loaded lots of new messages. So I guess, it was running in the morning but not really working.