Jump to content

Crash when closing atlas

Recommended Posts

When I close atlas executed via `0ad -editor` or any other method, the whole X session crashes and I am sent back to the tty.

This is the whole output:


TIMER| LoadDLL: 51.5459 ms
TIMER| InitVfs: 60.9659 ms
Writing the mainlog at /home/badosu/.config/0ad/logs/mainlog.html
TIMER| CONFIG_Init: 1.39374 ms
Sound: AlcInit success, using OpenAL Soft
TIMER| shutdown ConfigDB: 0.696 us
TIMER| resource modules: 85.1935 ms
TIMER TOTALS (9 clients)
  tc_pool_alloc: 0 c (0x)
  tc_png_decode: 0 c (0x)
  tc_dds_transform: 0 c (0x)
  tc_transform: 0 c (0x)
  tc_plain_transform: 0 c (0x)
  tc_ShaderGLSLLink: 0 c (0x)
  tc_ShaderGLSLCompile: 0 c (0x)
  tc_ShaderValidation: 0 c (0x)
  xml_validation: 0 c (0x)
TIMER| shutdown misc: 179.959 us
TIMER| InitVfs: 66.646 ms
Writing the mainlog at /home/badosu/.config/0ad/logs/mainlog.html
TIMER| CONFIG_Init: 1.56701 ms
Sound: AlcInit success, using OpenAL Soft
Unknown cache/TLB descriptor 0xc3
UserReport written to /home/badosu/.config/0ad/logs/userreport_hwdetect.txt
TIMER| RunHardwareDetection: 18.4556 ms
TIMER| InitRenderer: 847.828 us
TIMER| ps_console: 1.43787 ms
TIMER| ps_lang_hotkeys: 603.365 us
TIMER| shutdown TexMan: 15.603 us
TIMER| shutdown Renderer: 1.80881 ms
TIMER| shutdown SDL: 532.909 us
TIMER| shutdown UserReporter: 0.325 us
TIMER| shutdown ConfigDB: 0.196 us
TIMER| resource modules: 536.941 ms
TIMER TOTALS (0 clients)
TIMER| shutdown misc: 172.355 us
Profiler2.cpp(236): Assertion failed: "ThreadUtil::IsMainThread()"
os_path.h(48): Assertion failed: "(unsigned)wstring[i] <= (unsigned)UCHAR_MAX"
Assertion failed: "(unsigned)wstring[i] <= (unsigned)UCHAR_MAX"
Location: os_path.h:48 (OsString)

Call stack:

(0x558f2ad700e6) /usr/bin/pyrogenesis(+0x5dc0e6) [0x558f2ad700e6]
(0x558f2ad22962) /usr/bin/pyrogenesis(+0x58e962) [0x558f2ad22962]
(0x558f2ad23d3c) /usr/bin/pyrogenesis(+0x58fd3c) [0x558f2ad23d3c]
(0x558f2ad2441a) /usr/bin/pyrogenesis(+0x59041a) [0x558f2ad2441a]
(0x558f2ad736bf) /usr/bin/pyrogenesis(+0x5df6bf) [0x558f2ad736bf]
(0x558f2ad232be) /usr/bin/pyrogenesis(+0x58f2be) [0x558f2ad232be]
(0x558f2ad23d49) /usr/bin/pyrogenesis(+0x58fd49) [0x558f2ad23d49]
(0x558f2ad2441a) /usr/bin/pyrogenesis(+0x59041a) [0x558f2ad2441a]
(0x558f2aa6f6a7) /usr/bin/pyrogenesis(+0x2db6a7) [0x558f2aa6f6a7]
(0x558f2aa6f725) /usr/bin/pyrogenesis(+0x2db725) [0x558f2aa6f725]
(0x7f76b7407537) /usr/lib/libc.so.6(+0x3e537) [0x7f76b7407537]
(0x7f76b74076ee) /usr/lib/libc.so.6(+0x3e6ee) [0x7f76b74076ee]
(0x7f76b2fb0b01) /usr/lib/libgdk-x11-2.0.so.0(+0x61b01) [0x7f76b2fb0b01]
(0x7f76b7e1769e) /usr/lib/libX11.so.6(_XIOError+0x4e) [0x7f76b7e1769e]
(0x7f76b7e156aa) /usr/lib/libX11.so.6(+0x416aa) [0x7f76b7e156aa]
(0x7f76b7e10bff) /usr/lib/libX11.so.6(XSync+0x4f) [0x7f76b7e10bff]

errno = 0 (No error reported here)
OS error = ?


Link to post
Share on other sites

I just noticed there's a more appropriate subforum: Bug Reports, feel free to move and sorry!

As an addendum this started to happen after a fairly major upgrade including gtk, X11, nvidia drivers, kernel, etc...

Link to post
Share on other sites
1 hour ago, badosu said:

Well, in my case, since I'm working on random generated maps I don't lose my work but I can't also verify it easily (as I could with atlas by reproducing same seed, inspecting gens, etc.)

I mean the first time it happened, all my aside work was wasted :/

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...