Crashing on launching GUI or manually starting from system tray

[clone545]

MM was fine until recent config change enabling starting with Windows (10), and minimise to system tray, (possible start minimised too).

MM now starts with Windows (as expected) though crashes silently when trying to manually start from the system tray icon, or (more importantly) opening the GUI from the system tray.

MM runs fine and still functions normally if left alone, though no longer able to access GUI to change settings at all. Appears config is saved somewhere though am unable to clear this config as GUI does not load instead crashing out MM. Have tried launching from different locations, different versions, though no avail.

Win 10: 3.4.1 & 3.5.0 (non-MS Store)

[clone545]

Turns out I found this in event viewer for it:

Faulting application name: Move.Mouse.exe, version: 3.5.0.0, time stamp: 0x5bbd2bb6 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc00000fd Fault offset: 0x00007ffec2086568 Faulting process ID: 0x3214 Faulting application start time: 0x01d496aec9f77430 Faulting module path: unknown Report ID: 05055c57-7f9b-485a-8f60-376c3b889699 Faulting package full name: Faulting package-relative application ID:

[sw3103]

Hi @clone545,

Functionally, not a lot changed between 3.4.1 and 3.5.0. The automatically launch at Windows logon and minimise to System tray features have been there for quite a few releases.

The biggest change was the new UI, which I am worried may be the cause of this issue, although the event log entry you have supplied doesn't suggest so.

I've tried to re-create your issue unsuccessfully. Would you be able to post the following file so that I can see if it causes me the same issues?

%AppData%\Ellanet\Move Mouse\Settings.xml

Thanks

[clone545]

Hi @sw3103,

Yeah it's a bit odd, It was fine until i made that change.

It's not letting me upload the .xml, so i've had to just rename it to a .txt which should be attached. Move Mouse.txt

Cheers

[clone545]

@sw3103 Since you pointed me to the config, i've managed to get it to show the GUI now at least.

Line 22: True I've changed that to False and now it launches the GUI normally, and doesn't crash. That said, with it running, minimised to the system tray, right-click > Start does still cause it to crash out, so it might be an issue with the True on Line 23.

[ghost]

Windows 10 Pro 1803 build 17134.472: I had to remark out _moveMouse.ShowInTaskbar = true in SystemTrayIcon.ShowMoveMouse as it was causing a stack overflow in the MouseForm_Resize event (which sets ShowInTaskbar to configured value). Seems to be working without issue once I remarked this out.

[sw3103]

Windows 10 Pro 1803 build 17134.472: I had to remark out _moveMouse.ShowInTaskbar = true in SystemTrayIcon.ShowMoveMouse as it was causing a stack overflow in the MouseForm_Resize event (which sets ShowInTaskbar to configured value). Seems to be working without issue once I remarked this out.

Good find. I am going to release a new version without the KryptonWinFormControls package, which I suspect is the cause of these crashes.

[stefanbalan]

Hi, I'm a recent user of this app and I came here to find if this issue is known. I also suspected the Krypton controls to be at fault, I removed them and the stack overflow exception goes away. Should I create a pull request?

[sw3103]

Version 3.6.0 now available without KryptonWinFormControls UI components.