The bug started since JJ+ 5,7 was applied. As far as I know, it only affects Windows 7 users.
If you close the main game window the chat-logger window remains frozen (see pic).
If you close the chat-logger window instead, the game appears to close but its "Jazz2.exe" process keeps running. So, once you open JJ2 with 5.7+ on Windows 7, the only way to close it is to kill the process.

Thanks for the report! This is very concerning and it's good to learn about it. Can you take a look in your plus.ini file? There are two settings in the [Logging] section, "Chatlog" and "AutoSaveChatlog," which could be related: can you report the results of each combination of those settings? i.e.

• Chatlog=True, AutoSaveChatlog=True
• Chatlog=True, AutoSaveChatlog=False
• Chatlog=False, AutoSaveChatlog=True
• Chatlog=False, AutoSaveChatlog=False

The bug occurs as reported when Chatlog=True and doesn't occur when Chatlog=False .
The value of AutoSaveChatlog has no influence on the bug as far as I can tell.

To be more specific, when you have Chatlog=True but AutoSaveChatlog = False, closing the Jazz2 window first results in frozen chatlog, closing the chatlog window leaves the game running, but closing the game afterwards still leaves the residual "Jazz2.exe" process active.

And it doesn't matter whether anything gets written to the chatlog window at any point before you close the game?

No. With settings Chatlog=True and AutoSaveChatlog = False, I just opened the game and closed it (via its main window), and the chatloger window froze as usual.

The only text file that was modified/created was the Jazz2.log file, but that seems to happen regardless of whether you have Chatlog=True (and the bug) or Chatlog=False (and no bug).

Actually, scratch that. I've been able to get it to close without a bug by entering a level and saying a thing. It's weird. I will check this out more.

Here's what I found. If you have spy enabled, the bug always occurs. If you have spy disabled, the bug occurs only if you close the game during the game menu. It doesn't occur if you have nospy and are closing during a lvl.

Very strange. What if you use the -nolog command line option?

The -nolog command seems to have no effect whatsoever.
The bug doesn't occur if you disable spy and close mid-game/mid-level. It also doesn't occur at all if you completely disable Chatlog. It must be somehow related to the Chatlogger imho.

It also doesn't occur if you attach Cheat engine to the jazz2.exe process and enable speed hack (no need to actually change the speed), but I have no idea what that means .

Edit: so it occurs if you have:
1) Chatlog = True .and Spy on and close the game, or
2) Chatlog = True, and noSpy on, and close the game while not mid-level.

Clarification: you need to enter a level that starts up the chatlog in order to prevent the bug.
Just going in single player and closing is the same as closing the game mid-menu (chatlogger windows freezes).

Originally Posted by Zero[CDF]

Clarification: you need to enter a level that starts up the chatlog in order to prevent the bug.
Just going in single player and closing is the same as closing the game mid-menu (chatlogger windows freezes).

I worry this is conflating two factors: single player vs. multiplayer, and empty chatlog vs. non-empty chatlog. What if you play a single player level that does write to the chatlog? For example, any level with a script should write a " (loaded script module *.j2as)" line.

You're right. I misattributed the behavior.
If I play the Holyday Hare 18 via single player the bug still happens.
I have to be closing the game in a level loaded with party mode (and no spy) to prevent the bug.
Also, the bug still occurs if I close a game opened with party-mode -> local split-screen
I have to select other party-mode options in order to prevent it.

Give this a try. It's working for me on a Windows 7 virtual machine.

That seems to fix the problem. Thanks .

Really glad to hear it! This fix will be available in 5.8 as well as the above download link.