From: Lars Andersen <expez@expez.com>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 16420@debbugs.gnu.org
Subject: bug#16420:
Date: Sun, 12 Jan 2014 19:27:07 +0100 [thread overview]
Message-ID: <CACMT31PC2aW=aSxXBM75qtRDgYoiGn-X-_d9tq4-gxF9SNT40g@mail.gmail.com> (raw)
In-Reply-To: <52D2DA3A.80700@swipnet.se>
[-- Attachment #1: Type: text/plain, Size: 1885 bytes --]
The RES column does not grow. I'm dual booting on that computer, so I
tried reproducing the bug under Windows 7 without success.
At this point is there anything to be learned from attaching GDB, or is
this indeed someone else's problem at this point? If I were to file this
bug elsewhere, I'd be happy to get any pointers as to what information I
should include in the report.
Lars
On Sun, Jan 12, 2014 at 7:08 PM, Jan Djärv <jan.h.d@swipnet.se> wrote:
> Hello.
>
> 2014-01-12 18:26, Lars Andersen skrev:
>
>> (overlays-in (point-min) (point-max)) returns what you would expect:
>> #<overlay from 397 to 400 in *scratch*>
>>
>> This was with a slightly altered example, I removed the overly long
>> comment as
>> it took forever to draw. 100% cpu resources are used when the line is
>> being
>> drawn, and it seems to be redrawn many times before it's finally done.
>> Then
>> all is well until something causes the line to be redrawn.
>>
>> I'm not sure what 'RSS' means in this context, but I assumed you wanted a
>> screenshot of top:
>> http://imgur.com/Rv7Z5Ly
>>
>
> RSS is the RES column. Does it grow?
>
>
>> Unfortunately emacs isn't shown here, but X always takes the blame for the
>> resource use, never emacs. I have tried interrupting whatever is going on
>> with C-g after toggling debug-on-error, but I'm unable to interrupt
>> anything
>> in this manner.
>>
>> FWIW I cannot reproduce this bug on any other computers either. My
>> desktop
>> computer runs an almost identical software stack but is unaffected.
>>
>> I will try to attach a debugger, but my computer is quite unusable after
>> triggering this problem, so it may be difficult.
>>
>
> This sounds like an X server bug. As Emacs is not using much CPU it isn't
> inflooping and sending lots of X requests at least.
>
> Jan D.
>
>
>
[-- Attachment #2: Type: text/html, Size: 2698 bytes --]
next prev parent reply other threads:[~2014-01-12 18:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 22:01 bug#16420: 24.3; Drawing an overlay causes 100% cpu utilization Lars Andersen
2014-01-12 16:04 ` Dmitry Antipov
2014-01-12 16:30 ` Eli Zaretskii
2014-01-12 17:53 ` Jan Djärv
2014-01-12 18:00 ` Eli Zaretskii
2014-01-12 18:03 ` Michael Heerdegen
2014-01-13 5:45 ` Dmitry Antipov
2014-01-13 9:35 ` Lars Andersen
2014-01-13 10:04 ` Dmitry Antipov
2014-01-13 10:56 ` Lars Andersen
2014-01-12 17:26 ` bug#16420: Lars Andersen
2014-01-12 18:08 ` bug#16420: Jan Djärv
2014-01-12 18:27 ` Lars Andersen [this message]
2014-01-12 18:32 ` bug#16420: Eli Zaretskii
2014-01-12 18:49 ` bug#16420: Jan Djärv
2016-08-09 1:40 ` bug#16420: npostavs
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACMT31PC2aW=aSxXBM75qtRDgYoiGn-X-_d9tq4-gxF9SNT40g@mail.gmail.com' \
--to=expez@expez.com \
--cc=16420@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).