You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
0198:err:winediag:wined3d_adapter_create Using the Vulkan renderer for d3d10/11 applications.
05f4:err:wininet:HTTP_ParseRfc850Date unexpected month format L" Dec 2024 08:04:00 UTC"
05f4:err:wininet:HTTP_ParseDate unexpected date format L"Thu, 12 Dec 2024 08:04:00 UTC"
0614:err:winediag:ntlm_check_version ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
01c8:err:msync:msync_wait_multiple Unexpected kernel return code: 0xf (os/kern) invalid name
01c8:err:msync:server_register_wait Failed to send server register wait: 0x1000000a
The last two errorlog lines repeated around a gazillion times. Granted, the Windows app was indeed incompatible with Whisky, DXVK or Metal, but IMHO Whisky should still concatenate such repeating errors. As a result, I had a logfile that's 10 GB of just that error, line after line. Found it only thanks to my script I use to look up misbehaving or runaway logs and other support files in ~/Library/Application Support to clean up after my own projects when I make a mistake (easy to do).
IMHO any logging should always have a sanity check - if the very same error repeats 100,000,000 times line after line, it shouldn't be written out to the log 100,000,000 times, period.
Steps to reproduce
Try to run an incompatible exe that fails silently at kernel or graphics framework emulation level, yet doesn't exit
See the same error accumulate in the log
Run out of free disk space
Expected behaviour
Repeated, exact same errors that directly follow each other should be sanity checked and concatenated in the log, instead of just writing them out a billion of times. Such infinitely repeating exact same errors should not have been even piped to the log system in the first place, as that itself might bring any machine to its knees.
Logs
Are you really sure you want me to upload a 10 GB logfile here? I mean, it would probably compress down to ~10 MB, being so ridiculously low on entropy, but I am not really keen on trying to open the 10 GB file in vi to sanitise all my PII like user paths and system UIIDs... /s
What version of Whisky are you using?
2.3.2
What version of macOS are you using?
Sonoma (macOS 14)
Issue Language
Yes my issue is written in English
The text was updated successfully, but these errors were encountered:
Description
0198:err:winediag:wined3d_adapter_create Using the Vulkan renderer for d3d10/11 applications.
05f4:err:wininet:HTTP_ParseRfc850Date unexpected month format L" Dec 2024 08:04:00 UTC"
05f4:err:wininet:HTTP_ParseDate unexpected date format L"Thu, 12 Dec 2024 08:04:00 UTC"
0614:err:winediag:ntlm_check_version ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
01c8:err:msync:msync_wait_multiple Unexpected kernel return code: 0xf (os/kern) invalid name
01c8:err:msync:server_register_wait Failed to send server register wait: 0x1000000a
The last two errorlog lines repeated around a gazillion times. Granted, the Windows app was indeed incompatible with Whisky, DXVK or Metal, but IMHO Whisky should still concatenate such repeating errors. As a result, I had a logfile that's 10 GB of just that error, line after line. Found it only thanks to my script I use to look up misbehaving or runaway logs and other support files in ~/Library/Application Support to clean up after my own projects when I make a mistake (easy to do).
IMHO any logging should always have a sanity check - if the very same error repeats 100,000,000 times line after line, it shouldn't be written out to the log 100,000,000 times, period.
Steps to reproduce
Expected behaviour
Repeated, exact same errors that directly follow each other should be sanity checked and concatenated in the log, instead of just writing them out a billion of times. Such infinitely repeating exact same errors should not have been even piped to the log system in the first place, as that itself might bring any machine to its knees.
Logs
What version of Whisky are you using?
2.3.2
What version of macOS are you using?
Sonoma (macOS 14)
Issue Language
The text was updated successfully, but these errors were encountered: