[A16] Switching windows causes lockup (Edit - Possibly a Linux only issue)

Started by shentino, March 30, 2017, 04:42:14 AM

Previous topic - Next topic

shentino

When I use alt-tab to switch out of fullscreen mode during map generation, everything goes dark.  Task manager cites the rimworld process as being stuck at 0 percent cpu and when I switch back to the full screen rimworld, everything goes black.

Circumstances:

Full screen, 1024x768, gentoo linux, kernel 4.10.6, version alpha 16, steam as of March 30 2017.

Happened:

Screen go black and rimworld stops

Expected:

Screen repaint with standard prompt and CPU keeps busy mapgenning

Reproduce:

Start rimworld in fullscreen, start a new game, and alt-tab in the middle of generating the map

Savegame:

N/a

Logfile:



[attachment deleted by admin due to age]

Calahan

Thank you for the bug report.

I just tried to reproduce this error using Windows (8.1), but I was unable to cause a crash while alt-tabbing during (100%) world creation. If I left focus away from the game for long enough then the CPU usage did drop to 0% (RAM usage was stable), and when I returned focus to the game again then the screen was black for a short time (with a blue spinning cursor). But after ~15 seconds the world map appeared, and the game returned to normal functioning. So maybe this is a Linux / Gentoo Linux only issue? (if anyone reading this is running Linux / Gentoo Linux, and feeling helpful, it would be appreciated if you could try and reproduce the crash the OP experienced).

World generation is the most (system) resource intensive part of the creating a new game, so I'm pretty sure this crash is due to this. Although can I please ask about when you alt-tabbed back to the black screen the first time, how long did you leave it there? As the game might still be initialising the world even without any on-screen activity even with no CPU activity, like what happened when I tried to reproduce this issue. If you left it on the black screen for at least five minutes then that does sound like it crashed, but if it was only for a few seconds then I wouldn't be so sure the program had stopped working (regardless of what Task Manager is reporting). Also you say the CPU usage was 0%, but what about RAM usage. Was that also 0%, or static, or ?? Can you please repeat your test, and when you focus / alt-tab back to the game for the first time, can you please leave it on the black screen (without doing anything else on the computer, not even clicking the mouse) for at least five minutes and report back on the result (namely whether or not the game recovered).

Finally, I have edited your thread title to reflect my failure to reproduce this on Windows, and the possibility that this is a Linux only issue.

shentino

Ram usage was a full 1G or so according to task manager.

And yeah, it just...hung.  At the very least, it hung at least thrice as long as it normally takes if I don't tab.  Not to mention that failure to handle a repaint/expose signal, at least when rimworld's own OSD dialog box shows a progressive "..." to report progress, which should IMHO have kept the window updated.

Also, my map size was 400x400


shentino

I used GDB to do a backtrace, it appears to be hanging on a futex

(gdb) bt
#0  0x00007fbe7a1a3357 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0, futex_word=0x7fbe74e64890)
    at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  do_futex_wait (sem=sem@entry=0x7fbe74e64890, abstime=0x0) at sem_waitcommon.c:111
#2  0x00007fbe7a1a3404 in __new_sem_wait_slow (sem=0x7fbe74e64890, abstime=0x0) at sem_waitcommon.c:181
#3  0x0000000000f08819 in ?? ()
#4  0x0000000000f02d27 in ?? ()
#5  0x00000000007c8f73 in ?? ()
#6  0x00000000004661bb in ?? ()
#7  0x00007fbe78a32700 in __libc_start_main (main=0x4651a0, argc=3, argv=0x7fff7639a638, init=<optimized out>,
    fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff7639a628) at ../csu/libc-start.c:289
#8  0x000000000046f695 in ?? ()
#9  0x00007fff7639a628 in ?? ()
#10 0x000000000000001c in ?? ()
#11 0x0000000000000003 in ?? ()
#12 0x00007fff7639bca0 in ?? ()
#13 0x00007fff7639bcb7 in ?? ()
#14 0x00007fff7639bcc0 in ?? ()
#15 0x0000000000000000 in ?? ()

Ark

Linux Mint 17.3, kernel 3.19, 2560x1600, RimWorld 0.16.1393 rev546 drm free.
Tried a couple of times, everything works as expected. Planet and colony maps generate normally, even if tabbed out.


[attachment deleted by admin due to age]

shentino

I would be willing to submit a core dump and copy of the executable to a trusted developer if that would help.

Said person would at the least need to have staff credentials or the endorsement of someone who does.

ison

Thanks for reporting, but I'm not sure there's much we can do. It looks like a bug with Unity. We can only hope that updating Unity will solve this issue.