Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: gnus quietly quits in background?
Date: Sun, 19 Feb 2012 09:47:50 +0100	[thread overview]
Message-ID: <87r4xrryyx.fsf@gnus.org> (raw)
In-Reply-To: <87vcn3rzna.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Right.  I've now instrumented `kill-buffer' so that it'll give me a
> backtrace when something tries to kill the group buffer.

And I got a backtrace.

The code is:

(defun gnus-html-image-fetched (status buffer image)
  "Callback function called when image has been fetched."
  (unless (plist-get status :error)
[...]
    )
  (kill-buffer (current-buffer)))

So when we get an :error, sometimes the http buffer doesn't exist?
That's just weird.

Debugger entered: nil
  (progn (debug))
  (if (and (bufferp buffer) (or (equal (buffer-name buffer) "*Group*") (and (> (length (buffer-name buffer)) 10) (equal (substring (buffer-name buffer) 0 8) "*Summary")))) (progn (debug)))
  (when (and (bufferp buffer) (or (equal (buffer-name buffer) "*Group*") (and (> (length (buffer-name buffer)) 10) (equal (substring (buffer-name buffer) 0 8) "*Summary")))) (debug))
  kill-buffer(#<buffer *Summary nntp+news.gmane.org:gwene.com.hacker-news.full*>)
  gnus-html-image-fetched((:error (error connection-failed "deleted\n" :host "gifninja.com" :service 80)) nil ("http://gifninja.com/animatedgifs/647830/buffer.gif"))
  apply(gnus-html-image-fetched ((:error (error connection-failed "deleted\n" :host "gifninja.com" :service 80)) nil ("http://gifninja.com/animatedgifs/647830/buffer.gif")))
  url-queue-callback-function((:error (error connection-failed "deleted\n" :host "gifninja.com" :service 80)) [cl-struct-url-queue "http://gifninja.com/animatedgifs/647830/buffer.gif" gnus-html-image-fetched (nil ("http://gifninja.com/animatedgifs/647830/buffer.gif")) t #<killed buffer> 1329640750.369599 nil t])
  apply(url-queue-callback-function ((:error (error connection-failed "deleted\n" :host "gifninja.com" :service 80)) [cl-struct-url-queue "http://gifninja.com/animatedgifs/647830/buffer.gif" gnus-html-image-fetched (nil ("http://gifninja.com/animatedgifs/647830/buffer.gif")) t #<killed buffer> 1329640750.369599 nil t]))
  url-http-activate-callback()
  url-http-async-sentinel(#<process gifninja.com> "deleted\n")
  delete-process(#<process gifninja.com>)
  byte-code("\302\303\b\304H	>\204.




  reply	other threads:[~2012-02-19  8:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-18  8:51 Eric Abrahamsen
2012-02-18  9:05 ` Eric Abrahamsen
2012-02-18  9:11 ` Adam Sjøgren
2012-02-18  9:36   ` Eric Abrahamsen
2012-02-18 10:13 ` Antoine Levitt
2012-02-18 10:35 ` Steinar Bang
2012-02-18 12:59 ` Lars Ingebrigtsen
2012-02-18 15:07   ` Antoine Levitt
2012-02-18 21:38     ` Lars Ingebrigtsen
2012-02-19  1:28       ` Eric Abrahamsen
2012-02-19  8:33         ` Lars Ingebrigtsen
2012-02-19  8:47           ` Lars Ingebrigtsen [this message]
2012-02-19  8:50             ` Lars Ingebrigtsen
2012-02-20  2:36               ` Eric Abrahamsen
2012-02-20  7:15                 ` Lars Ingebrigtsen
2012-02-20 11:32                   ` Eric Abrahamsen
2012-02-20 12:15                     ` Lars Ingebrigtsen
2012-02-21  6:01                       ` Eric Abrahamsen
2012-02-19  0:02   ` Eric Abrahamsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r4xrryyx.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).