bug#5074: Emacs just aborted during url download

bug#5074: Emacs just aborted during url download

[Lennart Borgman]

I have no backtrace, nothing. All I know is that it was probably
during an url-retrieve-synchronously or during a (redisplay t).

On w32. mingw. My patched version. 2009-11-05.

bug#5074:

[Glenn Morris]

Nobody can do anything with this information.

Please reopen this if you ever get a backtrace, or a reproducible
crash recipe, in an unpatched Emacs.

bug#5074:

[Lennart Borgman]

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.
There was just a new bug report about url-retrieve-synchronously (bug
6274). I suspect it can be related.

I also reported a hang in the same function in bug 5103 and another
hang calling it in a timer in bug 5372.




(I have no patches that I think can be related to this, but I can be wrong.)


On Wed, May 26, 2010 at 7:40 PM, Glenn Morris <rgm@gnu.org> wrote:
>
> Nobody can do anything with this information.
>
> Please reopen this if you ever get a backtrace, or a reproducible
> crash recipe, in an unpatched Emacs.
>
>
>
>

bug#5074:

[Juanma Barranquero]

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.

> 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.

> 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

bug#5074:

[Lennart Borgman]

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
>

bug#5074:

[Juanma Barranquero]

On Wed, May 26, 2010 at 23:51, Lennart Borgman
<lennart.borgman@gmail.com> wrote:

> 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 don't doubt you're experiencing trouble. Myself, I've had a lot more
crashes in the past month than the year before... which isn't entirely
unexpected, now that the trunk is open again.

Out of curiosity, which compiler are you using? I recently had lots of
problems with MinGW 4.5.0, apparently unrelated to the one described
in etc/PROBLEMS.

    Juanma

bug#5074:

[Lennart Borgman]

On Thu, May 27, 2010 at 12:47 AM, Juanma Barranquero <lekktu@gmail.com> wrote:
>
> I don't doubt you're experiencing trouble. Myself, I've had a lot more
> crashes in the past month than the year before... which isn't entirely
> unexpected, now that the trunk is open again.
>
> Out of curiosity, which compiler are you using? I recently had lots of
> problems with MinGW 4.5.0, apparently unrelated to the one described
> in etc/PROBLEMS.

A maybe old version:

  gcc (GCC) 3.4.5 (mingw-vista special r3)
  Copyright (C) 2004 Free Software Foundation, Inc.