[LINUX][BUG][11.2] Duplicate process.

[Rehtinor]

When launching LOVE projects on linux a second process is created also called 'love'. This additional process remains after closing the game window. These additional processes build up in the background until manually terminated. As you can see the processes only consume a little bit of memory and nothing else. I am running the love 11.2 AppImage on Debian Buster.

Screenshot_20190812_174009.png (113.85 KiB) Viewed 5285 times

The attachment Screenshot_20190812_174213.png is no longer available

[Rehtinor]

Seems running default 'love' without a project does not have this issue but running a 'game.love' or 'love <folder>' does. I am using a completely blank 'main.lua' for testing, running other love games also does this.

[slime]

The no-game screen has the audio, sound, and joystick modules disabled, whereas an empty project has every module enabled – I guess one of those modules is causing it. Maybe you could narrow it down?
It's likely one of LÖVE's dependencies is the root issue (e.g. OpenAL Soft or one of its backends like pulseaudio, or SDL or one of its joystick backends like udev).

[Rehtinor]

Tried disabling various modules then disabled all but window and event, issue persisted. Where is the source for the default project so I can pack it into a love and try running it?

[Rehtinor]

Seems the issue has something to do with launching the project from the 'love.desktop' file with an argument. Launching directly from terminal does not have this issue, odd behavior.

EDIT: Here is the memory dump of the duplicate process, this process is created when running love.AppImage directly BUT is not automatically closed if running love using the 'love.desktop' file.

Private
988 KB [heap]
108 KB /usr/local/bin/love
100 KB /usr/lib/x86_64-linux-gnu/libfuse.so.2.9.9
32 KB [stack]
24 KB /usr/lib/x86_64-linux-gnu/libc-2.28.so
8 KB /usr/lib/x86_64-linux-gnu/libdl-2.28.so
8 KB /usr/lib/x86_64-linux-gnu/libz.so.1.2.11
8 KB /usr/lib/x86_64-linux-gnu/libpthread-2.28.so
8 KB /usr/lib/x86_64-linux-gnu/ld-2.28.so

Shared
920 KB /usr/lib/x86_64-linux-gnu/libc-2.28.so
156 KB /usr/lib/x86_64-linux-gnu/ld-2.28.so
116 KB /usr/lib/x86_64-linux-gnu/libfuse.so.2.9.9
112 KB /usr/lib/x86_64-linux-gnu/libz.so.1.2.11
84 KB /usr/lib/x86_64-linux-gnu/libpthread-2.28.so
8 KB /usr/lib/x86_64-linux-gnu/libdl-2.28.so

EDIT: Setting 'Terminal=1' in the 'love.desktop' file causes the other process to properly close when the window is closed.

[pgimeno]

libfuse? I have no idea how AppImage works but the fact it uses libfuse suggests to me that that process is some kind of AppImage stub. I don't think PhysFS or any other part of LÖVE uses fuse.

[Rehtinor]

Your right running the love binary package instead of the AppImage does not have the secondary process. Unfortunately I don't know much about AppImage either. Running other AppImage applications does have a second process appear, however it closes when the main window does. Seems something specifically about the love AppImage is the issue.

EDIT: Heres a dump from the Tiled AppImage secondary process

Private
884 KB [heap]
112 KB /usr/local/bin/tiled
96 KB /usr/lib/x86_64-linux-gnu/libfuse.so.2.9.9
44 KB [stack]
24 KB /usr/lib/x86_64-linux-gnu/libc-2.28.so
8 KB /usr/lib/x86_64-linux-gnu/libz.so.1.2.11
8 KB /usr/lib/x86_64-linux-gnu/libpthread-2.28.so
8 KB /usr/lib/x86_64-linux-gnu/libdl-2.28.so
8 KB /usr/lib/x86_64-linux-gnu/ld-2.28.so
Shared
916 KB /usr/lib/x86_64-linux-gnu/libc-2.28.so
156 KB /usr/lib/x86_64-linux-gnu/ld-2.28.so
120 KB /usr/lib/x86_64-linux-gnu/libfuse.so.2.9.9
112 KB /usr/lib/x86_64-linux-gnu/libz.so.1.2.11
84 KB /usr/lib/x86_64-linux-gnu/libpthread-2.28.so
8 KB /usr/lib/x86_64-linux-gnu/libdl-2.28.so