Andrzej Wójcik (Tigase) opened 1 month ago
|
|||||
Andrzej Wójcik (Tigase) changed state to 'In Progress' 1 month ago
|
|||||
Andrzej Wójcik (Tigase) added "Related" #621 1 month ago
|
|||||
Andrzej Wójcik (Tigase) added "Related" #628 1 month ago
|
|||||
Hmm... I'm yet again in the state of "flickering". Running beagle from shell doesn't result in any logs there. And in Console.app (with search/filter for "beagle" there is not much either):
In Beagle I got a couple of sudden disconnects:
|
|||||
Andrzej Wójcik (Tigase) added "Related" tigase/_server/server-core#1551 1 month ago
|
|||||
Andrzej Wójcik (Tigase) added "Related" #639 2 weeks ago
|
|||||
To deal with this issue, I've decided to update version of Martin library (#639) to include changes in asynchronous processing and multithreading. After fixing a few deadlocks and an error that could lead to connection not being able to reconnect (after receiving `stream:error/), I was able to find issue with memory management that would lead to crashes from #638 & #632. Additionally, I've identified a memory leak related to joining to MUC room that would result in a XMPP connection not being fully removed from the memory. That caused account to be in incorrect state and conversations not disappearing from the conversations list. As those changes are quite large, I would keep running a new version for a few days to ensure that it is stable enough to be released as a beta build. |
Type |
Bug
|
Priority |
Normal
|
Assignee | |
Version |
5.3.6
|
Sprints |
n/a
|
Customer |
n/a
|
In some cases, BeagleIM after disconnection from Wifi (swich) or after suspension fails to reconnect ending with blocked account. In this state it is not possible to disable nor enable the account.