[Linux] Recurring 1.092 CTD

[ChildeR]

I get a CTD after a couple of centuries of play. I can reproduce it by firing up an observe game and letting it run - it almost never completes. The stack trace is always similar:

Error: Received signal 11
Error: Received signal 11
./ck2(_Z15sigsegv_handleri+0x21)[0x8a1f63b]
./ck2(_Z15sigsegv_handleri+0x21)[0x8a1f63b]
[0xf76ea400]
[0xf76ea400]
./ck2(_ZN10CCharacter14PassOnHoldingsEPS_bR3CIDP5CListIS0_Eb[0xf76ea430+0x]
3dba)[0x83e7a16]
/lib/i386-linux-gnu/libc.so.6(gsignal+0x4f)[0xf72d61df]
/usr/lib32/fglrx/dri/fglrx_dri.so(+0x1bee313)[0xf6894313]
/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xf7293d4c]
/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xf7396d3e]
./ck2(_ZN10CCharacter7OnDeathEbb13ECauseOfDeathj+0x1006)[0x83ab89a]
./ck2(_ZN10CCharacter13CheckForDeathEv+0x572)[0x83cff80]
./ck2(_ZN10CCharacter19MonthlyUpdateSerialEv+0xb7a)[0x83b13b8]
./ck2(_ZN10CCharacter17DailyUpdateSerialEv+0x1d1c)[0x83a5988]
./ck2(_ZN10CGameState11DailyUpdateEv+0x30c)[0x86fee74]
./ck2(_ZN10CGameState15HandleDailyTickERK6CArrayIiE+0x163e)[0x86fe9f8]
./ck2(_ZN17CDailyTickCommand7ExecuteEv+0x1d)[0x88bb929]
./ck2(_ZN8CSession6UpdateEv+0x2be)[0x8a77852]
./ck2(_ZN14CCKApplication6UpdateEv+0x28)[0x84ccdae]
./ck2(_ZN12CInGameIdler4IdleEb+0x206)[0x86414b8]
./ck2(_ZN12CApplication14UpdateOneFrameEb+0x196)[0x8a1fa74]
./ck2(_ZN12CApplication3RunEv+0x2e)[0x8a1fb52]
./ck2(main+0x45e6)[0x875e712]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0xf72c14d3]
./ck2[0x830c311]
Segmentation fault (core dumped)

Linux desktop (Ubuntu 12.10, 64-bit), fglrx, AMD Radeon HD 7770.

 

[Urzhail64]

If it's related to autosave or save...it's a common problem. Paradox has not officially said anything on this.

 

[ChildeR]

If you mean this issue, no one there posted a stack trace so I'm not sure if it's the same issue, but I've had no save corruption. The most recent autosave has always been playable. The trace looks like it has to do with character deaths and inheritance, not saving.

(Besides, there is confirmation they are working on it.)

 

[Dracko81]

More likely the final patrician dieing bug then savegame for sure. But being Linux, I wouldn't want to speculate.

 

[balmung60]

The final patrician dying (particularly via assassination/other violence) is definitely a bug in Linux that causes CTDs. If you're having that problem, I'd recommend just searching all of the republics for a patrician with no heir and killing him via console (natural deaths (which includes console killing) don't trigger the bug) and hope that his replacement is more fertile.

You could also try deliberately assassinating an entire patrician family and see if you get the same error.

 

[ForzaA]

From what I can see, this is likely a bug that we've recently found and fixed (possibly for a hotfix) - someone (most likely a patrician) died without an heir, while having a retinue.

 

[unmerged(320188)]

I've had random CTDs too playing on PC since latest patch. The game became unplayable because of the random CTDs. Not sure what caused it hope a hotfix is inbound.

 

[AndrewT]

I've had random CTDs too playing on PC since latest patch. The game became unplayable because of the random CTDs. Not sure what caused it hope a hotfix is inbound.

There are two crash issues in vanilla 1.092: one relating to autosaves, and one relating to retinues attached to a republic patrician who dies without heir - do either of those sound like your problem?