Crash during Character creation

[Hormalakh]

[Description of the issue]

Game crashes if I mess with the character class selection too much. It was already starting to slow down with every new selection I made.



[DETAILED list of steps to reproduce the issue AND what to look for]

Example:

1) Start new game
2) Skip blank black screen that shows up with the chirping birds by clicking a bunch of times.
3) Click on the culture at the top of the screen to randomize selections.
4) Go back to race selection.
5) Mess with races a bit. Selected Aumaua, island. Female.
6) Selected rogue, then paladin, then priest, then barbarian.
7) After barbarian, game crashed.



[Expected behaviour]

It should allow me to reselect a new class without crashing



[Other remarks / Comments]
First time playing, could be an issue with my PC.



[Files]
dxdiag

[special]
Your forum won't let me upload gameoverlayrenderer.log file so I've copy/pasted the info here:
------
Wed Aug 20 12:02:55 2014 UTC - GameOverlay process started: pid: 2464
Wed Aug 20 12:02:55 2014 UTC - GameOverlay process connecting to: pid: 3604
Wed Aug 20 12:02:55 2014 UTC - BuildID: 1407966480
Wed Aug 20 12:02:55 2014 UTC - Steam Path: C:\Program Files\Steam
Wed Aug 20 12:02:58 2014 UTC - Generating new string page texture 2735: 256x256, total string texture memory is 262.14 KB
Wed Aug 20 12:02:58 2014 UTC - Generating new string page texture 2736: 128x256, total string texture memory is 393.22 KB
Wed Aug 20 12:04:31 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:04:41 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:04:51 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:05:01 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:07:47 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:07:57 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:08:07 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:08:17 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:08:27 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:08:37 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:08:47 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:08:58 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:09:08 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:09:18 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:09:28 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:09:38 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:09:48 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:09:59 2014 UTC - Warning: The game hasn't rendered a frame from us in over 10 seconds
Wed Aug 20 12:10:07 2014 UTC - Detected possibly crashed/killed game, exiting
Wed Aug 20 12:10:07 2014 UTC - Shutting down overlay
-----

DxDiag.txt

output_log.txt

Edited August 20, 2014 by Hormalakh

[Hormalakh]

I believe this is due to a memory leak. Running win7 32-bit.

 

It also happens when I "undress my aumaua"

Edited August 20, 2014 by Hormalakh