1. We have a QA initiative where we work with the community more closely than ever to get your bug reports into the hands of the developers. Please use this forum for LIVE Server bug reporting. Do follow the format below, because it will help us out greatly in responding. If you do not, it's possible your bug report will be misinterpreted, or worse, lost!

    Read BEFORE submitting your first bug: Reporting Bugsā€¦ QA 101 Document
    • Search for your bug before posting in order to avoid duplicate reports.
    • Only reply to an existing thread if you have additional information for the reported bug. ALL extraneous commentary will be deleted to avoid cluttering the reports.
    • Keep your bug report short and factual.
    • There is no need to submit crash logs. Crash data we require is automatically logged.
    Bug Report Template
    1. Title:
    2. Reproduction Rate:
    3. Blocker?
    4. Details:
    5. Steps to Reproduce:
    6. User Specs:
    To get started, use /bug in-game (/devbug if on QA) to auto-create this template. It will even auto-fill some of the required information and open the browser for you. Then take the information that was just saved to your system's clipboard and paste it into a new QA forum post. Thank you bug hunters!
Dismiss Notice
This Section is READ ONLY - All Posts Are Archived

[Known] Crashed when logging out

Discussion in 'Offline Mode' started by Chatele, Mar 5, 2018.

  1. Chatele

    Chatele Avatar

    Likes Received:
    Trophy Points:
    I decided to create a new char on off line mode to see how char creation changed, if any.... When I went to log out, the game hung, could not read the error message, had to tab out and click, close all windows on the SOTA icon to shut it down. .
  2. liz_the_wiz

    liz_the_wiz Bug Brigade - Bug Hunter

    Likes Received:
    Trophy Points:
    Ive seen the same, quit leads to crash.
  3. Lexie

    Lexie Bear Queen

    Likes Received:
    Trophy Points:
    A prior bug has been re-opened. I could be wrong, but I think it is also related to memory leaks. I've seen this behavior as well.
    Bug #: 50406
    Chatele likes this.