[Users] [Bug 3139] New: Main window totally unresponsive due to a busy loop

[noreply at thewildbeast.co.uk]

http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3139

            Bug ID: 3139
           Summary: Main window totally unresponsive due to a busy loop
    Classification: Unclassified
           Product: Claws Mail
           Version: 3.9.3
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P3
         Component: UI
          Assignee: users at lists.claws-mail.org
          Reporter: deweloper at wp.pl

I am using claws-mail-3.9.3-1.fc20.i686 and I have a POP3 (TLS) account which
locks up the program every time I try to fetch e-mails from it.
After entering password and accepting their certificate GUI locks up totally -
no reaction to events, no repainting, 1 CPU core hogged (100%)

The busy loop is at inc.c:858-860.

#0  session_is_running (session=session at entry=0x877c250) at session.c:243
#1  0x080f59c3 in inc_pop3_session_do (session=0x8783388) at inc.c:858
#2  inc_start (inc_dialog=inc_dialog at entry=0x8795670) at inc.c:631
#3  0x080f70b8 in inc_all_account_mail (mainwin=0x84d9ec8, autocheck=1,
notify=0) at inc.c:384
#4  0x080f8042 in defer_check_all (data=data at entry=0x1) at main.c:313
#5  0x48066262 in g_timeout_dispatch (source=source at entry=0x86fa738,
callback=0x80f8020 <defer_check_all>, user_data=0x1) at gmain.c:4451
#6  0x48065556 in g_main_dispatch (context=0x8497de0) at gmain.c:3066
#7  g_main_context_dispatch (context=context at entry=0x8497de0) at gmain.c:3642
#8  0x48065920 in g_main_context_iterate (context=0x8497de0,
block=block at entry=1, dispatch=dispatch at entry=1, self=<optimized out>) at
gmain.c:3713
#9  0x48065dc3 in g_main_loop_run (loop=loop at entry=0x840a7e8) at gmain.c:3907
#10 0x4372d700 in IA__gtk_main () at gtkmain.c:1257
#11 0x080828cf in main (argc=1, argv=0xbffff214) at main.c:1551

Program never goes out of frame #1 above.
The issue is 100%-reproducible.
I tried Thunderbird and it fetches e-emails from that account with no problems.
Workaround: disable problematic account.

-- 
You are receiving this mail because:
You are the assignee for the bug.