Results 1 to 9 of 9

Thread: Re-sizing Console Windows kills KDE

  1. #1

    Default Re-sizing Console Windows kills KDE

    I've been having this issue for a while now, it doesn't happen 100% of the time, I believe it happens when memory is too full.

    I'm on OpenSuSE 12.2.

    I've tried different consoles that weren't built in (i.e. Terminator)

    Any thoughts or experience?

    It restarts my whole environment and I have no recourse, so I'm not sure how much work I've lost.

  2. #2
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,037
    Blog Entries
    14

    Default Re: Re-sizing Console Windows kills KDE

    Quote Originally Posted by charlieoliver View Post
    I've been having this issue for a while now, it doesn't happen 100% of the time, I believe it happens when memory is too full.

    I'm on OpenSuSE 12.2.

    I've tried different consoles that weren't built in (i.e. Terminator)

    Any thoughts or experience?

    It restarts my whole environment and I have no recourse, so I'm not sure how much work I've lost.
    "when memory is too full" is very "windows". If this happens now and then on heavier memory usage, the first thing I can think of is a broken RAM bar. You should run memtest, for at least 24 hours, and it may not produce one single error..

    A thing always to consider, is the videocard, brand and model please, and tell us whether you installed a driver for it.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  3. #3

    Default Re: Re-sizing Console Windows kills KDE

    k, I'll give memtest a go.
    Also, I'm on an AMD 6570M running fglrx drivers

  4. #4

    Default Re: Re-sizing Console Windows kills KDE

    Honestly, I don't know how to run memtest. Anyone have a clue if it could be related to video card? And why that would affect seemingly only console windows?

    Alternatively, if anyone can clue me into how to run memtest...

  5. #5

    Default Re: Re-sizing Console Windows kills KDE

    I'm really frustrated that this is a thing, I'm seriously thinking of switching distros, it just doesn't make any sense to me.

  6. #6
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,448
    Blog Entries
    2

    Default Re: Re-sizing Console Windows kills KDE

    I've been seeing the same thing, but for me it's Firefox (understandably), and especially if I put extra memory pressure by also running something else that's particularly memory intensive like a big virtual machine.

    On my 4GB system with 2GB swap,
    When I anticipate running into memory usage issues, (and afterwards to understand if memory is being returned or not) I run
    Code:
     # free
            total         used         free             shared    buffers     cached
    Mem:       4056824    2719060    1337764          0        135220     626240
    -/+ buffers/cache:      1957600    2099224
    Swap:      2095100         60    2095040
    In the above readout,
    I have noticed that swapping intensifies when Mem/free drops to about 130000 and it becomes more likely that Firefox will freeze and require forcibly closing.
    The sample readout indicates current Mem/free is approx 10x that amount, so I shouldn't experience app crashes.

    If you are on a system with minimal resources, maybe you should consider LXDE as an alternative desktop. The openSUSE default is somewhat similar to KDE (whereas the XFCE Desktop installs with Gnome applications).

    Also, you might benefit from an upgrade to 12.3. The version of systemd running on 12.3 instantiates consoles differently. Traditionally, when you run multiple versions of the same thing (eg consoles), each and every instance is a new, individual application requiring the same amount of memory for every additional instance. More advanced systemd instead spawns multiple instances of the same application, sharing most of the common processes thereby also using considerably less memory.

    HTH,
    TSU

  7. #7

    Default Re: Re-sizing Console Windows kills KDE

    Upgraded to 12.3 and no joy, it was so bad this past reboot that just attempting to bring the console window into focus was enough to kill my machine.

    I'm running an Intel i7 2630, 8 GB of RAM, and an AMD Radeon 6570M.

    I can't really picture why it would be that I wouldn't be able to handle a single VM, a browser, my IDE and a couple of console windows.

    Sorry, I'm just frustrated, and confused about why this is an issue.

  8. #8

    Default Re: Re-sizing Console Windows kills KDE

    Maybe it's this: https://bugs.kde.org/show_bug.cgi?id=310666
    The reporter there also uses the fglrx driver.

    You could try the workaround mentioned there and see if it doesn't crash then. Run Konsole by pressing Alt+F2 and entering:
    Code:
    konsole  --notransparency

  9. #9
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Re-sizing Console Windows kills KDE

    On 2013-06-14 01:46, tsu2 wrote:
    > Also, you might benefit from an upgrade to 12.3. The version of systemd
    > running on 12.3 instantiates consoles differently. Traditionally, when
    > you run multiple versions of the same thing (eg consoles), each and
    > every instance is a new, individual application requiring the same
    > amount of memory for every additional instance. More advanced systemd
    > instead spawns multiple instances of the same application, sharing most
    > of the common processes thereby also using considerably less memory.


    Are you sure of that?

    Windows was doing that back in 1995, so it is to me unbelievable that
    Linux starts to do it now. Shared code segments, separate data segments,
    and DLLs, etc. Linux had that since ages, too.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 12.3 x86_64 "Dartmouth" at Telcontar)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •