GNOME Bugzilla – Bug 733314
[IMAPx] Starved FETCH when using IDLE
Last modified: 2014-07-18 09:49:26 UTC
Created attachment 280967 [details] Camel debug log Attaching the last 1000 lines of a imapx:commmand debug log where imapx was waiting for a result of a FETCH that wasn't comming. This is with e-d-s at e60f804e9e116ae99c4103048332d04d40875ba3 the lates imapx fix.
(gdb) p camel_imapx_store_dump_queue_status(imapx_store) Queue status for server 0x2cba840: jobs:1 queued:0 active:1 done:0 Content of 'jobs': [0] job:0x433c230 (type:0x10 REFRESH_INFO) with pending commands:0 Content of 'active': [0] command:0x7ff164361650 for job:0x433c230 (type:0x10 REFRESH_INFO)
(gdb) bt full
+ Trace 233835
Created attachment 281007 [details] debug patch for evolution-data-server; Maybe it'll help on its own (I did one change there), but it'll give some mapping what is going on in the background at least. Please try with it, but also beware, it'll be very chatty on its own.
With attachemnt 281007 I am getting errors (the error bar in evolution pops up) from time to time that I wasn't getting before. Example: "Error while Retrieving folder list for yaneti@declera.com. Error fetching folders: got response tag unexpectedly: DONE" Here is the end of a strace of the server process at the time this happens, I'll shorten everyting but the reads and writes to fd 1: ..... write(1, "* STATUS INBOX (MESSAGES 33790 UIDNEXT 717504 UIDVALIDITY 125388"..., 130) = 130 read(0, "D00661 IDLE\r\n", 4308) = 13 write(1, "+ idling\r\n", 10) = 10 read(0, "DONE\r\n", 4295) = 6 write(1, "D00661 OK Idle completed.\r\n", 27) = 27 read(0, "D00662 STATUS INBOX.BG (MESSAGES UNSEEN UIDVALIDITY UIDNEXT HIGH"..., 4289) = 204 write(1, "* STATUS INBOX.BG (MESSAGES 1 UIDNEXT 3 UIDVALIDITY 1253885558 U"..., read(0, "", 4085) = 0 write(2, "imap(yaneti): Info: Connection closed in=12297 out=6514255\n", 59) = 59
Created attachment 281017 [details] debug patch ][ maybe now?
Created attachment 281022 [details] debug patch ]I[ A follow-up debug patch. The previous version was willing to issue DONE command multiple times (in yaneti's case twice) in a row. This should be avoided now.
I've got a confirmation from Yaneti on IRC, thus I follow what I suggested at bug #733081 comment #10. *** This bug has been marked as a duplicate of bug 733081 ***