From: Lennart Borgman <lennart.borgman@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 5074@debbugs.gnu.org
Subject: bug#5074:
Date: Wed, 26 May 2010 23:51:34 +0200 [thread overview]
Message-ID: <AANLkTimCehloF0bqYoyaybwe5mc4wygxuAuGWoDXzayE@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinZ9JdNt4hVs2R8z3mxG2TwsVqi-yVCwdnAcaND@mail.gmail.com>
On Wed, May 26, 2010 at 11:33 PM, Juanma Barranquero <lekktu@gmail.com> wrote:
> On Wed, May 26, 2010 at 20:20, Lennart Borgman
> <lennart.borgman@gmail.com> wrote:
>
>> I think it may be wrong closing this bug. You can not do anything with
>> this information alone, but please do not hide it by just closing it.
>
> But this bug report has *no* useful information, other than the fact
> that a non-reproducible crash happened perhaps during a call to
> url-retrieve-synchronously. Or perhaps during redisplay. There's not
> even a backtrace. It would be difficult to relate any possible fix to
> this bug.
Yes, sorry. I will try change my habit, always running Emacs under a debugger.
>> There was just a new bug report about url-retrieve-synchronously (bug
>> 6274). I suspect it can be related.
>
> Why? You reported a crash, #6274 talks about a temporary freeze.
Because all information about the function may be related. A bad call
to the system functions may result in a bad state resulting in a crash
or a hang. But ... since it is on different platforms with different
API:s you and Glenn are probably right here. There is probably no
connection between 6274 and this bug report.
However FYI I still have a lot of crashes/freezes. Emacs hangs and is
difficult to kill from Windows Task Manager, but it does not loop.
Seems to be low level. I suspect four sources at the moment: url
related (most suspected for hangs), frame related (very suspected for
crashes and a bit for hangs) and the current changes to the display
code (a little bit suspected for crashes). And my own changes for
frame handling (quite suspected, but they are very recent, last month
only). I will try to get back traces.
>> I also reported a hang in the same function in bug 5103 and another
>> hang calling it in a timer in bug 5372.
>
> Well, then perhaps these two bugs are really related to #6274 (it's
> difficult to say, because as usual your bug reports are pretty sparse,
> to say the least). But in any case, how are they related to #5074?
>
> Juanma
>
next prev parent reply other threads:[~2010-05-26 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 1:28 bug#5074: Emacs just aborted during url download Lennart Borgman
2010-05-26 17:40 ` bug#5074: Glenn Morris
2010-05-26 18:20 ` bug#5074: Lennart Borgman
2010-05-26 21:33 ` bug#5074: Juanma Barranquero
2010-05-26 21:51 ` Lennart Borgman [this message]
2010-05-26 22:47 ` bug#5074: Juanma Barranquero
2010-05-26 23:03 ` bug#5074: Lennart Borgman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimCehloF0bqYoyaybwe5mc4wygxuAuGWoDXzayE@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=5074@debbugs.gnu.org \
--cc=lekktu@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).