Bug#722322: mutt hangs occassionally while fetching (big) message via IMAP
Hi Antonio, On Fri, Sep 09, 2016 at 11:16:26AM +, Antonio Radici wrote: > Can you try it against 1.7.0-2? Now I was able to test it: I confirm, that it still happens (NeoMutt 20161126 1.7.1), but as you said, I am able to interrupt with the syscall Ctrl-C. Thanks, Marco
Bug#722322: mutt hangs occassionally while fetching (big) message via IMAP
Can you try it against 1.7.0-2?
Bug#722322: mutt hangs occassionally while fetching (big) message via IMAP
Hi, >Hi, >is this still the case? I believe this got fixed a while ago, if it's not the >case let us know! For me it is still case in mutt version 1.5.23-3. Thanks, Marco
Bug#722322: mutt hangs occassionally while fetching (big) message via IMAP
On Wed, Sep 07, 2016 at 05:53:14AM +, Antonio Radici wrote: > Control: tag -1 +moreinfo > > On Tue, Sep 10, 2013 at 11:09:00AM +0200, Joris Mooij wrote: > > Package: mutt > > Version: 1.5.21-6.3 > > Severity: normal > > > > Dear Maintainer, > > > > When fetching big messages (typically, 1MB or more) from an IMAP server, > > mutt > > sometimes hangs at some point, displaying e.g. "Fetching message... > > 2.4M/7.0M > > (34%)" and stalling at that point. Ctrl-C doesn't help, and waiting doesn't > > help either. I usually simply close the terminal and restart mutt and try > > again > > (which may work, or not), but of course that is not really a solution and > > this > > may cause me to loose the changes to the mailbox that I made before running > > into this problem. > > > > The issue is not very reproducible unfortunately, but I suspect that it has > > to > > do with the networking code, as I have the impression that the problem > > occurs > > more often on wifi than on cable. > > > > If you need more information, please let me know and I will see what I can > > do. > > > > Best wishes, > > Joris Mooij > > > > Hi, > is this still the case? I believe this got fixed a while ago, if it's not the > case let us know! > > BTW in 1.7.0-2 you will be able to Ctrl-C and interrupt the syscall. Hi, I haven't encountered this behavior for a long time now, so I guess that it has been fixed meanwhile. Best wishes, Joris
Bug#722322: mutt hangs occassionally while fetching (big) message via IMAP
Control: tag -1 +moreinfo On Tue, Sep 10, 2013 at 11:09:00AM +0200, Joris Mooij wrote: > Package: mutt > Version: 1.5.21-6.3 > Severity: normal > > Dear Maintainer, > > When fetching big messages (typically, 1MB or more) from an IMAP server, mutt > sometimes hangs at some point, displaying e.g. "Fetching message... 2.4M/7.0M > (34%)" and stalling at that point. Ctrl-C doesn't help, and waiting doesn't > help either. I usually simply close the terminal and restart mutt and try > again > (which may work, or not), but of course that is not really a solution and this > may cause me to loose the changes to the mailbox that I made before running > into this problem. > > The issue is not very reproducible unfortunately, but I suspect that it has to > do with the networking code, as I have the impression that the problem occurs > more often on wifi than on cable. > > If you need more information, please let me know and I will see what I can do. > > Best wishes, > Joris Mooij > Hi, is this still the case? I believe this got fixed a while ago, if it's not the case let us know! BTW in 1.7.0-2 you will be able to Ctrl-C and interrupt the syscall.
Bug#722322: mutt hangs occassionally while fetching (big) message via IMAP
On Wed, Dec 02, 2015 at 02:12:30PM +0100, Marco Balmer wrote: > > Special in this part, the e-mail was only 3KiB. But I think it is the same > case. > I can reproduce it every time. > Let me know, if necessary, how I can help. Can you reproduce always with the same mail? Or do you need a big mailbox to reproduce it? does it always happen at the same email? Cheers Antonio
Bug#722322: mutt hangs occassionally while fetching (big) message via IMAP
Dear Antonio, On Tue, Dec 01, 2015 at 03:07:10PM +, Antonio Radici wrote: > On Tue, Dec 01, 2015 at 02:31:41PM +0100, Marco Balmer wrote: > > Hi, > > > > I can confirm exactly described behaviour in my mutt environment. > > > > $ dpkg -l mutt > > ii mutt 1.5.23-3 amd64 > > > > $ mutt -d 5 > > [2015-12-01 14:03:00] 5< a0064 OK Fetch completed. > > [2015-12-01 14:03:00] IMAP queue drained > > [2015-12-01 14:03:00] WEED is Not > > [2015-12-01 14:03:00] WEED is Not > > [2015-12-01 14:03:00] WEED is Not > > [2015-12-01 14:03:00] WEED is Not > > [2015-12-01 14:03:00] WEED is Not > > [2015-12-01 14:03:00] WEED is Not > > [2015-12-01 14:03:00] WEED is Not > > [2015-12-01 14:03:00] WEED is Not > > [2015-12-01 14:03:00] IMAP queue drained > > >> HERE IT HANGS < > > can we get a stacktrace through gdb? $ apt-get install mutt-dbg $ gdb mutt > IT OCURES < CTRL-C Hole Nachricht... 0K/2.3K (0%) Program received signal SIGINT, Interrupt. 0x75d03e9d in __libc_recv (fd=4, buf=0xd2df80, n=5, flags=-1) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:29 29 ../sysdeps/unix/sysv/linux/x86_64/recv.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 0x75d03e9d in __libc_recv (fd=4, buf=0xd2df80, n=5, flags=-1) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:29 #1 0x76d35d16 in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28 #2 0x76d3091d in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28 #3 0x76d32248 in _gnutls_recv_int () from /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28 #4 0x76d32754 in gnutls_record_recv () from /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28 #5 0x00495cef in tls_socket_read (conn=, buf=0x822dc0 "p-50Click http://www.xx.de/sq_mi/public/alert/news/Delete.action?key=164-167-238-2-177-31-150-38-161-41-192-153-227-83-63-11-95-64-162-113-50-116-33-19-167-178-215-232-104;..., len=1024) at ../mutt_ssl_gnutls.c:112 #6 0x00497f27 in mutt_sasl_conn_read (conn=0x822c30, buf=0x822dc0 "p-50Click http://www.xx.de/sq_mi/public/alert/news/Delete.action?key=164-167-238-2-177-31-150-38-161-41-192-153-227-83-63-11-95-64-162-113-50-116-33-19-167-178-215-232-104;..., len=1024) at ../mutt_sasl.c:553 #7 0x00495185 in mutt_socket_readchar (conn=conn@entry=0x822c30, c=c@entry=0x7fffcd47 "") at ../mutt_socket.c:172 #8 0x004952cd in mutt_socket_readln_d ( buf=0xcdb580 "a0791 OK Fetch completed.", buflen=512, conn=0x822c30, dbg=dbg@entry=2) at ../mutt_socket.c:202 #9 0x0049d139 in imap_cmd_step (idata=idata@entry=0x823210) at ../../imap/command.c:112 #10 0x0049e4b8 in imap_exec (idata=idata@entry=0x823210, cmdstr=cmdstr@entry=0x4c3fdb "NOOP", flags=flags@entry=0) at ../../imap/command.c:244 #11 0x004a0810 in imap_check_mailbox (ctx=ctx@entry=0xd150e0, index_hint=index_hint@entry=0x7fffce64, force=force@entry=0) at ../../imap/imap.c:1420 #12 0x00447575 in mx_check_mailbox (ctx=0xd150e0, index_hint=0x7fffce64, lock=) at ../mx.c:1443 #13 0x00420370 in mutt_index_menu () at ../curs_main.c:491 #14 0x0040897d in main (argc=1, argv=) at ../main.c:1056 (gdb) Special in this part, the e-mail was only 3KiB. But I think it is the same case. I can reproduce it every time. Let me know, if necessary, how I can help. Thanks, Marco signature.asc Description: GnuPG/PGP Signature
Bug#722322: mutt hangs occassionally while fetching (big) message via IMAP
On Wed, Dec 02, 2015 at 01:26:34PM +, Antonio Radici wrote: > Can you reproduce always with the same mail? Or do you need a big mailbox to > reproduce it? does it always happen at the same email? Reproduce in my case means, that I can wait some hours and an e-mail will reproduce the behaviour. I think it does not need a big mailbox to reproduce it. It happens on different kind of e-mails. I will observe this better next days. Marco signature.asc Description: GnuPG/PGP Signature
Bug#722322: mutt hangs occassionally while fetching (big) message via IMAP
On Tue, Dec 01, 2015 at 02:31:41PM +0100, Marco Balmer wrote: > Hi, > > I can confirm exactly described behaviour in my mutt environment. > > $ dpkg -l mutt > ii mutt 1.5.23-3 amd64 > > $ mutt -d 5 > [2015-12-01 14:03:00] 5< a0064 OK Fetch completed. > [2015-12-01 14:03:00] IMAP queue drained > [2015-12-01 14:03:00] WEED is Not > [2015-12-01 14:03:00] WEED is Not > [2015-12-01 14:03:00] WEED is Not > [2015-12-01 14:03:00] WEED is Not > [2015-12-01 14:03:00] WEED is Not > [2015-12-01 14:03:00] WEED is Not > [2015-12-01 14:03:00] WEED is Not > [2015-12-01 14:03:00] WEED is Not > [2015-12-01 14:03:00] IMAP queue drained > >> HERE IT HANGS < can we get a stacktrace through gdb? Cheers Antonio
Bug#722322: mutt hangs occassionally while fetching (big) message via IMAP
Hi, I can confirm exactly described behaviour in my mutt environment. $ dpkg -l mutt ii mutt 1.5.23-3 amd64 $ mutt -d 5 [2015-12-01 14:03:00] 5< a0064 OK Fetch completed. [2015-12-01 14:03:00] IMAP queue drained [2015-12-01 14:03:00] WEED is Not [2015-12-01 14:03:00] WEED is Not [2015-12-01 14:03:00] WEED is Not [2015-12-01 14:03:00] WEED is Not [2015-12-01 14:03:00] WEED is Not [2015-12-01 14:03:00] WEED is Not [2015-12-01 14:03:00] WEED is Not [2015-12-01 14:03:00] WEED is Not [2015-12-01 14:03:00] IMAP queue drained >> HERE IT HANGS < Hope this helps, Marco signature.asc Description: GnuPG/PGP Signature
Bug#722322: mutt hangs occassionally while fetching (big) message via IMAP
Package: mutt Version: 1.5.21-6.3 Severity: normal Dear Maintainer, When fetching big messages (typically, 1MB or more) from an IMAP server, mutt sometimes hangs at some point, displaying e.g. Fetching message... 2.4M/7.0M (34%) and stalling at that point. Ctrl-C doesn't help, and waiting doesn't help either. I usually simply close the terminal and restart mutt and try again (which may work, or not), but of course that is not really a solution and this may cause me to loose the changes to the mailbox that I made before running into this problem. The issue is not very reproducible unfortunately, but I suspect that it has to do with the networking code, as I have the impression that the problem occurs more often on wifi than on cable. If you need more information, please let me know and I will see what I can do. Best wishes, Joris Mooij -- Package-specific info: Mutt 1.5.21 (2010-09-15) Copyright (C) 1996-2009 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 3.10-2-amd64 (x86_64) ncurses: ncurses 5.9.20130608 (compiled with 5.9) libidn: 1.28 (compiled with 1.25) hcache backend: tokyocabinet 1.4.48 Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +USE_SMTP -USE_SSL_OPENSSL +USE_SSL_GNUTLS +USE_SASL +USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL=/usr/sbin/sendmail MAILPATH=/var/mail PKGDATADIR=/usr/share/mutt SYSCONFDIR=/etc EXECSHELL=/bin/sh MIXMASTER=mixmaster To contact the developers, please mail to mutt-...@mutt.org. To report a bug, please visit http://bugs.mutt.org/. misc/am-maintainer-mode misc/autoconf-remove-am-c-prototypes.patch features/ifdef features/xtitles features/trash-folder features/purge-message features/imap_fast_trash features/sensible_browser_position features-old/patch-1.5.4.vk.pgp_verbose_mime features/compressed-folders features/compressed-folders.debian debian-specific/Muttrc debian-specific/Md.etc_mailname_gethostbyname.diff debian-specific/use_usr_bin_editor.diff debian-specific/correct_docdir_in_man_page.diff debian-specific/dont_document_not_present_features.diff debian-specific/document_debian_defaults debian-specific/assumed_charset-compat debian-specific/467432-write_bcc.patch debian-specific/566076-build_doc_adjustments.patch misc/define-pgp_getkeys_command.diff misc/gpg.rc-paths misc/smime.rc upstream/531430-imapuser.patch upstream/537818-emptycharset.patch upstream/543467-thread-segfault.patch upstream/542817-smimekeys-tmpdir.patch upstream/548577-gpgme-1.2.patch upstream/553321-ansi-escape-segfault.patch upstream/568295-references.patch upstream/547980-smime_keys-chaining.patch upstream/528233-readonly-open.patch upstream/228671-pipe-mime.patch upstream/383769-score-match.patch upstream/578087-header-strchr.patch upstream/603288-split-fetches.patch upstream/537061-dont-recode-saved-attachments.patch upstream/608706-fix-spelling-errors.patch upstream/620854-pop3-segfault.patch upstream/611412-bts-regexp.patch upstream/624058-gnutls-deprecated-set-priority.patch upstream/624085-gnutls-deprecated-verify-peers.patch upstream/584138-mx_update_context-segfault.patch upstream/619216-gnutls-CN-validation.patch upstream/611410-no-implicit_autoview-for-text-html.patch upstream/path_max misc/579967-fixes-german-translation.patch mutt.org mutt-patched/sidebar mutt-patched/sidebar-dotted mutt-patched/sidebar-sorted mutt-patched/sidebar-utf8 mutt-patched/multiple-fcc -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mutt depends on: ii libassuan02.1.1-1 ii libc6 2.17-92+b1 ii libcomerr21.42.8-1 ii libgnutls26 2.12.23-5 ii libgpg-error0 1.10-3.1 ii libgpgme111.4.3-0.1 ii libgssapi-krb5-2 1.11.3+dfsg-3 ii libidn11 1.28-1 ii libk5crypto3 1.11.3+dfsg-3 ii libkrb5-3 1.11.3+dfsg-3 ii libncursesw5 5.9+20130608-1 ii libsasl2-22.1.25.dfsg1-14 ii libtinfo5 5.9+20130608-1 ii libtokyocabinet9 1.4.48-2 Versions of packages mutt recommends: ii exim4-daemon-light [mail-transport-agent] 4.80-7+b1 ii libsasl2-modules
