Application freezes on quit

Bug #212807 reported by Andrew Williams
2
Affects Status Importance Assigned to Milestone
LottaNZB
Fix Released
High
Andrew Williams

Bug Description

Affects: 0.21pre

When quitting the application clears out the backend configuration before the updater thread has stopped, the thread continues processing update requests as it doesn't identify that "None" is a invalid connection state.

I have fixed this issue in the branch devel-logwindow

Revision history for this message
Severin H (severinh) wrote :

Fix merged to trunk.

I've never used LottaNZB to monitor a HellaNZB daemon running on another machine so I didn't/couldn't reproduce the bug. But if this one-line-fix is the solution for this issue...

Changed in lottanzb:
assignee: nobody → nikdoof
importance: Undecided → High
milestone: none → 0.2.1
status: New → Fix Committed
Revision history for this message
Andrew Williams (nikdoof) wrote :

I think this maybe a symptom of a much larger issue and further testing is required. I suspect that if the connection to the remote backend idles out (as some routers along your route may dictate a maximum connection time) then the state will be set to None, which in turn stops the client updating without any warning messages.

I'll continue investigating the issue and will post further bug reports if I discover the underlying cause, but for the moment this bug can be resolved off as it fixes the symptom causing the most issues.

Severin H (severinh)
Changed in lottanzb:
milestone: 0.2.1 → 0.3
Severin H (severinh)
Changed in lottanzb:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.