From: Eli Zaretskii <eliz@gnu.org>
To: michael_heerdegen@web.de
Cc: 12196@debbugs.gnu.org
Subject: bug#12196: 24.1.50; setting cache-long-line-scans to non-nil freezes Emacs
Date: Wed, 15 Aug 2012 19:36:05 +0300 [thread overview]
Message-ID: <834no4jeoa.fsf@gnu.org> (raw)
In-Reply-To: <87has6ysxn.fsf@web.de>
> Date: Tue, 14 Aug 2012 06:54:28 +0200
> From: Michael Heerdegen <michael_heerdegen@web.de>
>
> I recently found this variable in the manual: `cache-long-line-scans'.
>
> However, nearly every time I set it to a non-nil value, Emacs instantly
> freezes, C-g has no more effect.
For me, it didn't freeze, it simply announced that memory was
exhausted and I should exit and restart Emacs. Under a debugger I saw
that the region cache code tried to allocate some ridiculously large
chunk of memory, like 1.6 GB. This happened because some changes
about a year ago modified the memory allocation for the cache in a way
that made the cache data structure and the memory it allocated
inconsistent. So the cache became confused and tried to allocate
more and more memory.
Should be fixed now (revision 109631 on the trunk), please test.
next prev parent reply other threads:[~2012-08-15 16:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 4:54 bug#12196: 24.1.50; setting cache-long-line-scans to non-nil freezes Emacs Michael Heerdegen
2012-08-15 16:36 ` Eli Zaretskii [this message]
2012-08-24 12:19 ` Michael Heerdegen
2012-08-24 13:35 ` Eli Zaretskii
2012-08-26 11:53 ` Christopher Schmidt
2012-08-31 8:50 ` Eli Zaretskii
2012-09-10 10:28 ` Christopher Schmidt
2012-09-10 11:10 ` Eli Zaretskii
2012-09-10 13:19 ` Christopher Schmidt
2012-09-10 17:10 ` Eli Zaretskii
2012-09-10 17:31 ` Christopher Schmidt
2012-09-10 18:43 ` Eli Zaretskii
2012-09-17 17:17 ` Christopher Schmidt
2012-09-17 18:38 ` Eli Zaretskii
2012-09-17 18:53 ` Christopher Schmidt
2012-09-17 20:18 ` Eli Zaretskii
2012-09-18 7:25 ` Christopher Schmidt
2012-09-18 8:02 ` Eli Zaretskii
2012-08-26 15:58 ` Michael Heerdegen
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=834no4jeoa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12196@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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.