From: emacs user <user.emacs@gmail.com>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: 16039@debbugs.gnu.org
Subject: bug#16039: repeated emacs crashes (in GC?)
Date: Sun, 15 Dec 2013 19:17:20 +0200 [thread overview]
Message-ID: <CAK16+CcK0iRFDegJv1WUY-QRm=-CE+-pi-FPEazK15GHF07M2w@mail.gmail.com> (raw)
In-Reply-To: <CAK16+Cf3P9KRjDkjcpDPqdnFRfGVq=BhVKTu9KA2w_Fc7TYjzw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2889 bytes --]
Dear Eli and Mitsuharu, Please let me know if there is anything else I can
do, test patches or such. again, Emacs just does not ever crash for me
after the change mentioned below, a great relief. E
On Sat, Dec 7, 2013 at 10:29 PM, emacs user <user.emacs@gmail.com> wrote:
> so after running the same emacs session for 72 hours, during which I used
> vm many times and emacs used a total of 1.5 CPU hours, I think it is safe
> to say that this problem that caused frequent crashes is fixed by the
> increase in newlim as specified below. I hope something like this can be
> implemented in the emacs development version. Thanks for your help, best,
> E
>
>
> On Thu, Dec 5, 2013 at 8:54 AM, emacs user <user.emacs@gmail.com> wrote:
>
>> I managed to compile your mac port and inserted:
>>
>> newlim = (re_max_failures * ratio + 200000)*2;
>>
>> will let you know in a few days if I still see crashes.
>>
>>
>> On Thu, Dec 5, 2013 at 2:35 AM, YAMAMOTO Mitsuharu <
>> mituharu@math.s.chiba-u.ac.jp> wrote:
>>
>>> >>>>> On Wed, 04 Dec 2013 10:48:11 +0900, YAMAMOTO Mitsuharu <
>>> mituharu@math.s.chiba-u.ac.jp> said:
>>>
>>> >>> Having 136 thousand frames during GC is not unheard of.
>>>
>>> >> (/ 8720000.0 (* 136 1000))
>>> >> 64.11764705882354
>>>
>>> >> If each frame consumes more than 64 bytes, then it will use up
>>> >> 8720000B stack space.
>>>
>>> > FWIW, the default compiler for Xcode 4.0.2 on Mac OS X 10.6 with the
>>> > -O2 option seems to consume 64 bytes for each mark_object frame:
>>>
>>> > i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666)
>>> (dot 3)
>>>
>>> > _mark_object:
>>> > 00000000000008a0 pushq %rbp
>>> > 00000000000008a1 movq %rsp, %rbp
>>> > 00000000000008a4 movq %rbx, 0xffffffffffffffd8(%rbp)
>>> > 00000000000008a8 movq %r12, 0xffffffffffffffe0(%rbp)
>>> > 00000000000008ac movq %r13, 0xffffffffffffffe8(%rbp)
>>> > 00000000000008b0 movq %r14, 0xfffffffffffffff0(%rbp)
>>> > 00000000000008b4 movq %r15, 0xfffffffffffffff8(%rbp)
>>> > 00000000000008b8 subq $0x40, %rsp
>>>
>>> > And the one for Xcode 5.0.2 on OS X 10.9 with -O4 does 24 bytes:
>>>
>>> > Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
>>>
>>> > _mark_object:
>>> > 0000000000005c70 pushq %rbp
>>> > 0000000000005c71 movq %rsp, %rbp
>>> > 0000000000005c74 pushq %r15
>>> > 0000000000005c76 pushq %r14
>>> > 0000000000005c78 pushq %r13
>>> > 0000000000005c7a pushq %r12
>>> > 0000000000005c7c pushq %rbx
>>> > 0000000000005c7d subq $0x18, %rsp
>>>
>>> I forgot to count the pushq instructions. The correct value would be
>>> 72 bytes for each mark_object frame in both cases.
>>>
>>> YAMAMOTO Mitsuharu
>>> mituharu@math.s.chiba-u.ac.jp
>>>
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 4297 bytes --]
next prev parent reply other threads:[~2013-12-15 17:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 14:55 bug#16039: repeated emacs crashes (in GC?) emacs user
2013-12-03 16:01 ` Eli Zaretskii
2013-12-04 0:43 ` YAMAMOTO Mitsuharu
2013-12-04 1:48 ` YAMAMOTO Mitsuharu
2013-12-05 0:35 ` YAMAMOTO Mitsuharu
2013-12-05 6:54 ` emacs user
2013-12-04 3:49 ` Eli Zaretskii
2013-12-04 6:33 ` emacs user
2013-12-07 20:29 ` emacs user
2013-12-15 17:17 ` emacs user [this message]
2013-12-15 17:45 ` Eli Zaretskii
2014-01-18 16:06 ` emacs user
2016-05-28 15:08 ` Alan Third
2016-11-03 22:45 ` emacs user
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='CAK16+CcK0iRFDegJv1WUY-QRm=-CE+-pi-FPEazK15GHF07M2w@mail.gmail.com' \
--to=user.emacs@gmail.com \
--cc=16039@debbugs.gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.