[Render] Quitting Freelancer on dx9 (dxwrapper) doesn't actually kill the process

[Render] Quitting Freelancer on dx9 (dxwrapper) doesn't actually kill the process - Printable Version

+- Discovery Gaming Community (https://discoverygc.com/forums)
+-- Forum: Discovery Development (https://discoverygc.com/forums/forumdisplay.php?fid=7)
+--- Forum: Discovery Mod General Discussion (https://discoverygc.com/forums/forumdisplay.php?fid=37)
+---- Forum: Discovery Mod Bug Reports (https://discoverygc.com/forums/forumdisplay.php?fid=573)
+----- Forum: Can't reproduce (https://discoverygc.com/forums/forumdisplay.php?fid=691)
+----- Thread: [Render] Quitting Freelancer on dx9 (dxwrapper) doesn't actually kill the process (/showthread.php?tid=209488)

Pages: 1 2

[Render] Quitting Freelancer on dx9 (dxwrapper) doesn't actually kill the process - Loophole - 09-17-2025

Type: Render
Bug: Quitting Freelancer on dx9 (dxwrapper) doesn't actually kill the process

Reproduction Steps:

On DSLauncher: click "Render Mode" and select DirectX 9 (dxwrapper); Use Desktop Resolution ON; Windowed Mode OFF (i.e. exclusive fullscreen on)
Launch Game, wait for it to load
Quit the game
Notice how the Freelancer.exe process still exists in the task manager (under the details tab).

Expected behaviour: Kill the Freelancer.exe process. This doesn't happen on DirectX 8 (native).

RE: [Render] Quitting Freelancer on dx9 (dxwrapper) doesn't actually kill the process - Aingar - 09-21-2025

Pushed a renderer related update just now that might have resolved this issue, please retest and report back.

RE: [Render] Quitting Freelancer on dx9 (dxwrapper) doesn't actually kill the process - Loophole - 09-21-2025

Hello. I've updated the launcher and tried again. It seems like it's still happening:
[Image: 5ArDjTO.png]

The launcher recognises the process and prompts to kill it when clicking "Launch Game":
[Image: Y6MsWYN.png]

Clicking "yes" indeed kills the process and starts a new one. Exiting the game doesn't kill the new process:
[Image: cTaQFfD.png]

RE: [Render] Quitting Freelancer on dx9 (dxwrapper) doesn't actually kill the process - Alex. - 01-11-2026

Cannot reproduce

RE: [Render] Quitting Freelancer on dx9 (dxwrapper) doesn't actually kill the process - Loophole - 01-11-2026

Will check again asap.

Still happening.
[Image: P2O950B.png]

Are there any logs or other kinds of outputs that I could provide to help debug this issue?

RE: [Render] Quitting Freelancer on dx9 (dxwrapper) doesn't actually kill the process - Groshyr - 01-11-2026

This occurrs because Freelancer would wait for an indefinitely running thread to finish. The following patch of DAlib.dll by BC46 would prevents Freelancer from running in the background after exiting the game in some cases: offset 0x004BF4, change FF to 00.

RE: [Render] Quitting Freelancer on dx9 (dxwrapper) doesn't actually kill the process - Alex. - 01-11-2026

Don't we already have that change as of Discovery 5.1, @Groshyr?

RE: [Render] Quitting Freelancer on dx9 (dxwrapper) doesn't actually kill the process - Groshyr - 01-11-2026

Quite sure I didn't bring it. Better double check it. I won't have access to my PC for another hour tho

RE: [Render] Quitting Freelancer on dx9 (dxwrapper) doesn't actually kill the process - Alex. - 01-11-2026

I am quite sure:

Quote:$ winpty python
Python 3.13.5 (tags/v3.13.5:6cb20a2, Jun 11 2025, 16:15:46) [MSC v.1943 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> f = open('EXE/DALib.dll', 'rb')
>>> f.seek(0x4BF4)
19444
>>> f.read(1)
b'\x00'
>>> exit()
$ git log EXE/DALib.dll
commit 512ec083d7085d159ab889c1c37cd07f5e062579
Author: Aingar <redacted>
Date: Fri May 31 21:15:57 2024 +0200

FF -> 00 dalib.dll 004BF4 BC46 Prevents Freelancer from running in the background after exiting the game in some cases. This occurred because Freelancer would wait for an indefinitely running thread to finish.

We are still missing reliable reproduction steps here.

RE: [Render] Quitting Freelancer on dx9 (dxwrapper) doesn't actually kill the process - Loophole - 01-11-2026

For what it's worth, I also have the same value on that address:

Quote:$ python
Python 3.13.11 (main, Dec 5 2025, 00:00:00) [GCC 15.2.1 20251111 (Red Hat 15.2.1-4)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> f = open('dalib.dll', 'rb')
>>> f.seek(0x4BF4)
19444
>>> f.read(1)
b'\x00'

$ md5sum dalib.dll
fcab0566fc7ea38c787d105f676af102 dalib.dll

I'm on Linux atm but I did reproduce the issue on Windows 11.
A note, I do use RTSS to bump the framerate to the highest legal value, and I've got NVIDIA's overlay running too. Could that change anything?