Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LOGFILE SPAM - repeating errors don't concatenate in logfiles, leading to a 10 GB (!) log with the same repeating error #1261

Open
1 task done
WWWFWWW opened this issue Dec 17, 2024 · 0 comments

Comments

@WWWFWWW
Copy link

WWWFWWW commented Dec 17, 2024

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

  1. Try to run an incompatible exe that fails silently at kernel or graphics framework emulation level, yet doesn't exit
  2. See the same error accumulate in the log
  3. 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant