teleport-freeze bug

[sujiniku]

If player try to use the teleport magic skill (i.e. push the hot key), then soon freeze computer. Not only Japanese mode, but also at English mode, Freeze bug happens.

[dorkster]

I am unable to reproduce this. Which map area were you in when this occurred?

[sujiniku]

Perhaps, this bug is caused by Japanese IME (Input Method) . When I pressed the hot key with Japanese IME turned on (i.e this mode is such "あ", "い" etc. are able to input), my computer freezes from time to time. Not only the key assigned to teleport but also other keys, the computer were frozen by the key pushed at Japanese IME turning on.

For example, at some text editor application(for example "gedit" ,"libre office writer" ) , if I push hot key "6" in when Japanese IME turning on, Japanese IME shows the conversion candidate such as below:

6 ６ 六 シックス six

[dorkster]

Hmm, so you're saying that enabling IME sometimes freezes your computer, even outside of Flare? That could be it, but just for the sake of completeness, I'd like to query:

• Your operating system
• Your version of SDL
• The version of Flare you using (I assume built from the latest git based on your contributions)

[sujiniku]

At out of flare game, the IME doesn't freeze computer.

Operating System: Fedora 27 (Linux) Workstation edition (i.e Desktop edition), 64 bit , Gnome 3.26.2 , SDL version: "SDL-1.2.15-29.fc27.x86_64 "
Flare version: built from the git download (2017, 11month/16day (Thursday) built from git)

[dorkster]

Might be something to do with SDL 1.2. I've been building/testing with SDL 2 exclusively for a while now.

[dorkster]

Hmm, I don't think the main branch can even be built with SDL 1.2 (we have a separate branch for that). So it's likely you built Flare with SDL 2. You can check this by running ldd flare to get a list of the libraries your compiled version is linked against.

Since you're building from source, let's try to get a backtrace of this crash. First build Flare with debugging symbols enabled:

cmake . -DCMAKE_BUILD_TYPE=Debug
make

Then run flare in gdb with:

gdb ./flare

When the game freezes, get a backtrace by simply entering the command backtrace into gdb. You can then copy and paste the output to this thread.

[sujiniku]

My computer uses SDL2. Because, debug information is "INFO: Using Render Device: SDLSoftwareRenderDevice (software, SDL 2)" .

Detail is such as below... " (gdb) r Starting program: /home/sujiniku/flare-game/flare Missing separate debuginfos, use: dnf debuginfo-install glibc-2.26-16.fc27.x86_64 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7ffff7fca700 (LWP 2247)] INFO: 1 joystick(s) found. INFO: Joy 0) MOSIC USB 2A8K GamePad
INFO: Using Render Device: SDLSoftwareRenderDevice (software, SDL 2) [New Thread 0x7fffd576e700 (LWP 2249)] "

[dorkster]

Great! Now, if you can get a backtrace when the freeze/crash happens, it would be very helpful in solving this.

[sujiniku]

Even this freeze bug happens, the monsters can move and the monsters can attack the player. Perhaps, this freeze bug may be occured by not accept input from players. There was no change in gdb even if this bug occurred.

When freezing bug occurs, the entire OS freezes, so I can not get debugging information.

At Fedora OS, not only Flare-game but also web browsers such as Firefox, there is a freezing bug that the entire OS freezes when the application freezes at inputing letters. Perhaps, This bug cause may be in Fedora side or IBus (IME) side .

[dorkster]

I'd like to clarify what you mean by "freeze". From what I can gather, Flare is continuing to run if monsters are moving/attacking. Is it only keyboard input that ceases to work, or is mouse input affected as well?

I've tried IBus+Anthy input on Arch Linux, but haven't had any luck reproducing the bug. So maybe it's Fedora specific?

[sujiniku]

As far as I have experienced this bug about 5-10 times, the computer didn't accept both mouse input and keyboard input . Not only flare but also OS (Fedora + Gnome) didn't accept both mouse input and keyboard. Therefore entire OS don't accept the input, user cannot use computer unless reboot the computer.