Really slow and painful crash

Discussion in 'Support!' started by nathan173ab, June 4, 2014.

  1. nathan173ab

    nathan173ab New Member

    Messages:
    15
    Likes Received:
    3
    I was playing a 1v1 match. Two planets, a moderately sized one and a tiny one. This was on Linux Mint 13 KDE. Game has probably been going on for about 40 minutes then all of the sudden the game's performance slows down, stutters, comes back to normal for some seconds, then completely locks up my whole computer and after sitting there for a minute or two waiting and hoping for it to unfreeze I finally decide that I just have to restart my computer. While I was waiting, I noticed my hard drive indicator was solidly lit so it seemed to be doing something. My guess is that it was a memory leak and was trying to access a lot of virtual memory. I'm not sure, but everything became so slow I could never do anything to figure out what was going on. Couldn't pull up any debug screen or the system monitor (Linux equivalent of the Windows task manager). My system specs:

    Linux Mint 13 KDE
    Core i7 920 @ 3.32GHz
    6GB (3x2GB) DDR3 1333MHz RAM
    GeForce GTX 770

    While I've mentioned what happened here, I also might as well mention the separate bug where I was never able to enter in a chat message. While waiting for a game or in the game, I could type in a chat message but I could never enter it. Pressed enter and nothing happen. I don't recall having that problem on Windows.
  2. SXX

    SXX Post Master General

    Messages:
    6,896
    Likes Received:
    1,812
    If there was actual game crash you should always see it in game logs, e.g:
    Code:
    ~/.local/Uber\ Entertainment/Planetary\ Annihilation/log/
    If you can find here any log that end with crash just upload both log and crash dump here and then somebody from devs will able to check it.

    If you have other server of phone you might try to connect to your desktop via SSH and check if this will be active. It's will work in case of low RAM or GPU lockup / some driver failure.

    Known issue: PA#3448. This one should be fixed in next update.
  3. nathan173ab

    nathan173ab New Member

    Messages:
    15
    Likes Received:
    3
    Alright thanks. I found two log files, both of which were created within around ten minutes of each other. I uploaded them.

    Attached Files:

  4. waterlimon

    waterlimon Member

    Messages:
    61
    Likes Received:
    55
    This happens to me on windows all the time...

Share This Page