bug#1644: 23.0.60; Emacs client loops

bug#1644: 23.0.60; Emacs client loops

[Lennart Borgman (gmail)]

With a fresh checkout from today Emacs client seems to loop. I do not
know exactly what happens but I get a lot of message boxes saying
"Emacsclient ERROR" from it. Sometimes I am able to reboot, sometimes I
have to turn off the computer power.

emacsclientw.exe is called with only the file name as a parameter when
this happens.

Sorry for not giving more information right now, but it is a bit
cumbersome to collect it.

I do not see this error when I use an emacs + emacs client built 2008-11-24.



In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
 of 2008-12-19
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --no-opt --cflags
-Ic:/g/include -fno-crossjumping'

bug#1644: 23.0.60; Emacs client loops

[Jason Rumney]

Lennart Borgman (gmail) wrote:
> Sorry for not giving more information right now, but it is a bit
> cumbersome to collect it.
>   

Pertinent information would be whether you have applied your usual patches.

I cannot reproduce the problem here, having tried both with and without 
Emacs running.

bug#1644: 23.0.60; Emacs client loops

[Lennart Borgman]

On Sat, Dec 20, 2008 at 2:26 AM, Jason Rumney <jasonr@f2s.com> wrote:
> Lennart Borgman (gmail) wrote:
>>
>> Sorry for not giving more information right now, but it is a bit
>> cumbersome to collect it.
>>
>
> Pertinent information would be whether you have applied your usual patches.

This is without any patches (otherwise I would have said so).

> I cannot reproduce the problem here, having tried both with and without
> Emacs running.

I can reproduce it, but I have only done it using the Firefox add-on
"It's All Text" so far. I have no recipe starting from "emacs -Q", but
I thought that this must be a rather big bug.

bug#1644: 23.0.60; Emacs client loops

[Lennart Borgman]

On Sat, Dec 20, 2008 at 2:43 AM, Lennart Borgman
<lennart.borgman@gmail.com> wrote:
> On Sat, Dec 20, 2008 at 2:26 AM, Jason Rumney <jasonr@f2s.com> wrote:
>> Lennart Borgman (gmail) wrote:
>>>
>>> Sorry for not giving more information right now, but it is a bit
>>> cumbersome to collect it.
>>>
>>
>> Pertinent information would be whether you have applied your usual patches.
>
> This is without any patches (otherwise I would have said so).
>
>> I cannot reproduce the problem here, having tried both with and without
>> Emacs running.
>
> I can reproduce it, but I have only done it using the Firefox add-on
> "It's All Text" so far. I have no recipe starting from "emacs -Q", but
> I thought that this must be a rather big bug.

I am not sure yet, but I believe this might have been a problem with
the Firefox add-on. I contacted the author. He did not reply, but he
uploaded a new version. With this new version and a new Emacs I can no
longer reproduce the problem. (Please notice however that I have also
built a new Emacs today.)

bug#1644: 23.0.60; Emacs client loops

[Jason Rumney]

Lennart Borgman wrote:
> I am not sure yet, but I believe this might have been a problem with
> the Firefox add-on.

This is likely, given that emacsclient does not create any threads, and 
MessageBox (the windows api call used for displaying messages when not 
running at the command line) does not return until you dismiss the 
dialog. So if multiple emacsclient error dialogs are appearing on the 
screen at once as your report described, then there must be multiple 
instances running.

bug#1644: 23.0.60; Emacs client loops

[Lennart Borgman]

On Wed, Dec 24, 2008 at 11:59 AM, Jason Rumney <jasonr@f2s.com> wrote:
> Lennart Borgman wrote:
>>
>> I am not sure yet, but I believe this might have been a problem with
>> the Firefox add-on.
>
> This is likely, given that emacsclient does not create any threads, and
> MessageBox (the windows api call used for displaying messages when not
> running at the command line) does not return until you dismiss the dialog.
> So if multiple emacsclient error dialogs are appearing on the screen at once
> as your report described, then there must be multiple instances running.

Yes, I can confirm that this was the case. I was able to see that in
some further tests (where my pc was not completely blocked).

bug#1644: marked as done (23.0.60; Emacs client loops)

[Emacs bug Tracking System]

[-- Attachment #1: Type: text/plain, Size: 848 bytes --]


Your message dated Wed, 24 Dec 2008 18:59:55 +0800
with message-id <4952162B.6040403@f2s.com>
and subject line Re: bug#1644: 23.0.60; Emacs client loops
has caused the Emacs bug report #1644,
regarding 23.0.60; Emacs client loops
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
1644: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=1644
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 3173 bytes --]

From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: emacs-pretest-bug@gnu.org
Subject: 23.0.60; Emacs client loops
Date: Sat, 20 Dec 2008 00:31:36 +0100
Message-ID: <494C2ED8.5030005@gmail.com>

With a fresh checkout from today Emacs client seems to loop. I do not
know exactly what happens but I get a lot of message boxes saying
"Emacsclient ERROR" from it. Sometimes I am able to reboot, sometimes I
have to turn off the computer power.

emacsclientw.exe is called with only the file name as a parameter when
this happens.

Sorry for not giving more information right now, but it is a bit
cumbersome to collect it.

I do not see this error when I use an emacs + emacs client built 2008-11-24.



In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
 of 2008-12-19
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --no-opt --cflags
-Ic:/g/include -fno-crossjumping'



[-- Attachment #3: Type: message/rfc822, Size: 3353 bytes --]

From: Jason Rumney <jasonr@f2s.com>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 1644-done@emacsbugs.donarmstrong.com, emacs-pretest-bug@gnu.org
Subject: Re: bug#1644: 23.0.60; Emacs client loops
Date: Wed, 24 Dec 2008 18:59:55 +0800
Message-ID: <4952162B.6040403@f2s.com>

Lennart Borgman wrote:
> I am not sure yet, but I believe this might have been a problem with
> the Firefox add-on.

This is likely, given that emacsclient does not create any threads, and 
MessageBox (the windows api call used for displaying messages when not 
running at the command line) does not return until you dismiss the 
dialog. So if multiple emacsclient error dialogs are appearing on the 
screen at once as your report described, then there must be multiple 
instances running.