#3956: mutt 1.8.3 hangs on accessing Exchange via IMAP, when Outlook is used
simultaneously
---------------------+---------------------
  Reporter:  davee   |      Owner:  brendan
      Type:  defect  |     Status:  new
  Priority:  minor   |  Milestone:
 Component:  IMAP    |    Version:  1.8.3
Resolution:          |   Keywords:
---------------------+---------------------

Comment (by kevin8t8):

 I've been tracing things through, but haven't found the cause yet.

 Just for any other devs, the cmd_parse_fetch() for the flag changes is
 calling imap_set_flags().  This then triggers mutt_set_header_color() ->
 mutt_pattern_exec() -> MUTT_HEADER: -> msg_search() ->
 imap_fetch_message().  So that's why we see the BODY.PEEK being sent in
 a7164 before a7163 is even finished.

 When processing a7164, it marks a7163 done, so by the time it gets back to
 the outer imap_cmd_step(), all the idata->cmds are already done.  So the
 last "IMAP queue drained" we see in the log occurs then.

 At first I thought it was the nested imap call leaving something goofy,
 but I couldn't see any problems (yet).

 So the question is where is it hanging?  After the mx_check_mailbox(),
 check should be MUTT_FLAGS so it should be calling update_index().  After
 update_index(), it outputs a message that would be logged, so my best
 guess is in update_index().

 Dave, I'll create a patch file with some more debug statements, just so I
 can confirm or deny where it's freezing.  I would appreciate if you could
 apply it and try to recreate the freeze.

--
Ticket URL: <https://dev.mutt.org/trac/ticket/3956#comment:5>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

Reply via email to