Highly unstable

[stderr-to-devnull]

Current Behavior

Ran it for 3 days and during this time:

• frozen tray icon requiring end task
• following memory optimization, completely froze requiring end task
• tray icon disappears, requiring end task

Expected Behavior

The complete opposite of the above.

Steps to Reproduce

Install and use.

App Version

3.0.8

Windows Version

Windows 10

Additional Context

No response

Checklist

• I have searched the existing issues to make sure this bug has not been reported yet.
• I have tested with the latest version of the application.

[ParthProLegend]

WMC_issue.compressed.best.mp4

Here's the video showcasing the same. It remains stuck for hours on end.

P.S. Sorry for the music, I was listening while recording.

[ParthProLegend]

#190 (comment) I have tried this just now, and it has fully reset every setting/config. Will update if the issue occurs.

[ParthProLegend]

Reporting back, it is still occuring.

[IgorMundstein]

I'll look into it. It runs on an old framework that doesn't handle multitasking well. I'll probably have to bump the version and drop support for XP/2003.

[ParthProLegend]

I'll look into it. It runs on an old framework that doesn't handle multitasking well. I'll probably have to bump the version and drop support for XP/2003.

Damn, you are better than most other companies at maintaining compatibility. But, dropping support for them is better as they are less than 0.5%, and the people still on that OS don't even know how to upgrade or are just not considering.

Apart from that, are you ok? You were missing for quite a long time. I tried reaching you on linkedin to know the same. I hope everything's good.

[IgorMundstein]

@ParthProLegend Haha, true. Even bumping the framework to a minimum for older Windows like 7 and 2008 might have issues as well. I think it's 4.5.2.

My code isn't perfect, but it's well-tested. The fact that issues are happening mostly on newer Windows makes me think about where the issue is. The issues on modern OS versions are likely related to how Windows 10 and 11 handle memory and security. Modern builds use aggressive memory compression and features like Core Isolation, which restrict how utilities operate.

Even though the project targets .NET Framework 4.0, when running on Windows 10/11 it executes on top of the OS's modern runtime. This aligns perfectly with the reports in other open issues, where these clean, isolated crashes are strictly happening on modern Windows builds due to how the modern OS handles errors.

I’ve been thinking about it, and I think it's better to stick with .NET Framework 4.0 for now to keep things stable and avoid creating new runtime headaches. Instead of jumping to a new framework, I'm going to use AI to see what can be improved to handle these newer Windows restrictions better.

It could also be hardware, although that's a low possibility in my opinion, but one defective memory chip or ssd/hdd, or even cpu heating or cooking, etc. Since the app performs heavy operations that drastically spike activity on the memory controller and storage subsystem at once, if a machine has a marginally unstable RAM overclock or an SSD throttling while the kernel swaps pages, things can fail with a paging error or access violation. The Windows kernel rejects the call to protect itself, causing an isolated app crash without triggering a full system Blue Screen or reboot. So, anyone, please consider a small but possible hardware fault on your end as well.

[stderr-to-devnull]

please consider a small but possible hardware fault on your end as well

Not the case for my system. It's running 24/7, doing video encoding (8-16h sessions) and RAM heavy games. Rock solid. No blue screens. The memory was also tested with OCCT.

I can also report that running WinMemoryCleaner then clicking 'Optimize' will often (3 out of 5 times) result in a main menu total freeze and render the app inoperable, having to resort again to 'End Task'.

[IgorMundstein]

please consider a small but possible hardware fault on your end as well

Not the case for my system. It's running 24/7, doing video encoding (8-16h sessions) and RAM heavy games. Rock solid. No blue screens. The memory was also tested with OCCT.

I can also report that running WinMemoryCleaner then clicking 'Optimize' will often (3 out of 5 times) result in a main menu total freeze and render the app inoperable, having to resort again to 'End Task'.

That is good to know, and having rock-solid stability during video encoding and passing OCCT definitely rules out basic hardware degradation or catastrophic RAM failure on your machine.

However, the hardware angle here is a bit more nuanced. Because the app forces the Windows kernel to instantly flush and restructure system-wide memory lists, it triggers a massive, instantaneous I/O and memory controller spike. This type of sudden, localized burst can occasionally cause a native paging error or an access violation if the kernel drops the request to protect process integrity under sudden load—which results in an isolated app lockup or crash without ever destabilizing the rest of your system or triggering a Blue Screen.

The main menu freeze you described (3 out of 5 times) points heavily toward a deadlock or a thread block while waiting for a response from these restricted native calls. I’ve been analyzing this behavior, and it aligns with other open reports where these freezes or clean crashes happen strictly on modern Windows builds due to tighter security layers like Core Isolation or aggressive memory compression architectures.

I am currently investigating ways to optimize how the app manages these operations on top of modern Windows runtimes to prevent the interface from hanging when a call takes longer or gets dropped by the OS.