[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#13527: 24.2.92 + 24.2.93; Spawning child process: resource temporari
bug#13527: 24.2.92 + 24.2.93; Spawning child process: resource temporarily unavailable
Tue, 12 Feb 2013 18:21:08 +0100
Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2.91 (windows-nt)
Eli Zaretskii wrote:
>> From: "Sebastien Vauban" <address@hidden>
>> Cc: address@hidden
>> Date: Tue, 12 Feb 2013 10:21:49 +0100
>> > If the problem _always_ happens when you save that Org buffer, then it
>> > would be best to attach GDB to Emacs before you try saving the buffer,
>> > and also set a breakpoint in spawnve.
>> >> But I can already "positively" tell you that this "spawning child process"
>> >> error is something *new in 24.2.92* -- I reused 24.2.91 for a couple of
>> >> days
>> >> with no problem; using 24.2.92, I got stopped only after a couple of
>> >> hours.
>> > Could be a side effect of bugfixes in this area that were done between
>> > these two versions.
>> I'm sorry to tell you that the problem still occurs with Emacs 24.2.93:
> Little wonder, as nothing was done with this problem since 24.2.92.
Well, regarding bug#13546 (which I really think is another symptom than
bug#13527, that is sharing the same root cause), you wrote:
│ Meanwhile, I installed a couple of small changes that may or may not
│ solve this problem, so please be sure to try the next pretest binary
│ when it becomes available.
I saw the announcement about 24.2.93 mid or end of last week, and waited for
Dany to expose a binary with that one (compiled by him on the 8th of Feb).
Besides that, I have to admit I stopped using 24.2.92 as it really was
unusable, and not compatible with my past work load. Things are as simple as
that. But I know it does not help, neither you, neither me.
> You are the only user who sees this problem. If we want to have any
> chances of solving it before 24.3 is released, we must cut down on the
> response time. I last heard from you 3 weeks ago.
I'll try to stick using 24.2.93, and report whatever I can.
>> After a couple of hours, Emacs is unusable; I must restart it to be able to
>> send emails, or to get list of files returned by Helm. That is, the problem
>> seems to be related to communication with external processes.
> Subprocesses and communications are handled by the same
> infrastructure, so this is not surprising, either.
>> BTW, I think that the 2 following problems:
>> - bug#13527: Spawning child process: resource temporarily unavailable
>> - bug#13546: Error(s) when sending emails
>> are just 2 sides of the same coin.
> Quite possibly.