* CPU usage just having a big file aboard
@ 2005-03-16 18:22 Dan Jacobson
2005-03-17 4:43 ` Eli Zaretskii
2005-03-17 23:02 ` Richard Stallman
0 siblings, 2 replies; 3+ messages in thread
From: Dan Jacobson @ 2005-03-16 18:22 UTC (permalink / raw)
I noticed viewing a 2 MB file, the CPU meter would spring to life
every few seconds, even though it was in a long ago buried
buffer. Flyspell was off. top(1) showed it munched quite a bit.
Must cause more often garbage collection or something.
Killing that buffer stopped it. emacs21 21.3+1-9
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: CPU usage just having a big file aboard
2005-03-16 18:22 CPU usage just having a big file aboard Dan Jacobson
@ 2005-03-17 4:43 ` Eli Zaretskii
2005-03-17 23:02 ` Richard Stallman
1 sibling, 0 replies; 3+ messages in thread
From: Eli Zaretskii @ 2005-03-17 4:43 UTC (permalink / raw)
Cc: bug-gnu-emacs
> From: Dan Jacobson <jidanni@jidanni.org>
> Date: Thu, 17 Mar 2005 02:22:34 +0800
>
> I noticed viewing a 2 MB file, the CPU meter would spring to life
> every few seconds, even though it was in a long ago buried
> buffer. Flyspell was off. top(1) showed it munched quite a bit.
> Must cause more often garbage collection or something.
> Killing that buffer stopped it. emacs21 21.3+1-9
This is probably the sign of JIT Font-lock stealth fontification.
If so, this is normal.
Was JIT stealth fontification turned on in that buffer?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: CPU usage just having a big file aboard
2005-03-16 18:22 CPU usage just having a big file aboard Dan Jacobson
2005-03-17 4:43 ` Eli Zaretskii
@ 2005-03-17 23:02 ` Richard Stallman
1 sibling, 0 replies; 3+ messages in thread
From: Richard Stallman @ 2005-03-17 23:02 UTC (permalink / raw)
Cc: bug-gnu-emacs
I noticed viewing a 2 MB file, the CPU meter would spring to life
every few seconds, even though it was in a long ago buried
buffer. Flyspell was off. top(1) showed it munched quite a bit.
Must cause more often garbage collection or something.
Killing that buffer stopped it. emacs21 21.3+1-9
How about if you run Emacs under GDB, and next time this occurs,
you could try to stop Emacs during that flurry of activity.
The backtrace will tell us what the activity is for.
You might have to try stopping it several times before you catch
it during the flurry of activity, but that won't be much work.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-03-17 23:02 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-03-16 18:22 CPU usage just having a big file aboard Dan Jacobson
2005-03-17 4:43 ` Eli Zaretskii
2005-03-17 23:02 ` Richard Stallman
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.