[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


From: Jan Djärv
Subject: bug#16420:
Date: Sun, 12 Jan 2014 19:49:33 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0


2014-01-12 19:27, Lars Andersen skrev:

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.

XOrg bugs are reported in the freedesktop bugzilla.  There is a link here:


I suspect they might want to know the actual server version (xdpyinfo) and the X calls involved (see x_draw_underwave in xterm.c).
Including /var/log/Xorg.0.log is a good idea.

But if you have a newer Xorg version with the same driver (see Xorg.0.log, it is in there somewhere) that does not have the bug, or if there is a newer driver that works, it is probably fixed.

        Jan D.


On Sun, Jan 12, 2014 at 7:08 PM, Jan Djärv <address@hidden
<mailto:address@hidden>> wrote:


    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
        drawn, and it seems to be redrawn many times before it's finally done.
        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 
        screenshot of top:

    RSS is the RES column.  Does it grow?

        Unfortunately emacs isn't shown here, but X always takes the blame for 
        resource use, never emacs.  I have tried interrupting whatever is going 
        with C-g after toggling debug-on-error, but I'm unable to interrupt
        in this manner.

        FWIW I cannot reproduce this bug on any other computers either.  My
        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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]