Nightly: 21: Unhandled Exception without any device connected after some inactive time

[Ruediger]

Hello all,

I open a a new issue since the problem is definitely not ASCOM related. NINA runs into unhandled exception even without any connected device and without any activity in the application and the error message is identical to reported issue 638.

I think it is now clear, that something within NINA is going wrong.

Cheers
Rüdiger

[Stefan B]

What i can find is this issue here:
https://github.com/dotnet/wpf/issues/1269

Do you happen to have a monitor setup like this? Otherwise the search continues…

[Ruediger]

I have multimonitor (4x24”, 1x21”), but the exception happens without user interaction. No problems with other .net Apps.
So this linked issue is something different.
here the .net info:

C:\Users\Ruediger>dotnet --info
It was not possible to find any installed .NET Core SDKs
Did you mean to run .NET Core SDK commands? Install a .NET Core SDK from:
https://aka.ms/dotnet-download

Host (useful for support):
Version: 3.1.4
Commit: 0c2e69caa6

.NET Core SDKs installed:
No SDKs were found.

.NET Core runtimes installed:
Microsoft.NETCore.App 3.1.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

[Ruediger]

I also checked the windows logs whether I see another error around this time. No issue, no warnings.

[Stefan B]

The linked issue is not about .net in general but about windows presentation foundation. This is the UI Framework in use.

Are your two monitors arranged like in the issue description? And does it happen with only one monitor attached? Just want to rule out stuff.

[Ruediger]

No, the arrangement is different, All 5 monitors are arranged horizontally.

‌

[Stefan B]

Please try out if having only one monitor with nina will still produce this error. Having 5 monitors on an imaging system is rare and if that is the reason for this error would explain why no one else so far had this issue.

[Ruediger]

To be honest, I would try to avoid this test, because the complete multiscreen configuration gets lost (windows mixes everything up). When re-plugging the screens you will start over. This will probably end up in restoring an image for the workstation.

Just one note: Old NINA versions and other .net APPs run flawless on this multiscreen solution.

[Stefan B]

Yea the problem here is, if this is a WPF bug there is not much I can do. And the stack trace is not looking like anything nina related, as it only shows .net and wpf internals

[Ruediger]

I have just updated to the latest graphic drivers (AMD). Maybe that has an impact.

[Stefan B]

Issue #638 was marked as a duplicate of this issue.

[Stefan B]

As WPF is hardware accelerated having up-to-date graphics drivers can potentially help

[Ruediger]

Hi Stefan,
here a brief update: I have been running NINA for 6 hours now. Only a dry run with ASCOM and no clicking, but so far no crash.
I have the slight hope, that the driver update has improved the situation.

Cheers Rüdiger

‌

[Ruediger]

Bad news. Ran a sequence with ASCOM simulators and it crashed. Same error, but I attached log anyway.

[Stefan B]

Is it possible to give more specific details about the hardware in use?

I could for example find another issue that has a matching stack trace, which was caused by the logitech set point software for a specific mouse in use
https://developercommunity.visualstudio.com/content/problem/167357/overflow-exception-in-windowchrome.html

It would also make sense, as NINA uses a custom wpf window chrome too.
Do you have that in use too by any chance?

‌

[Ruediger]

Yes, SetPoint is installed. I have tried to trigger this event but even sending a horizontal scroll did not trigger the exception.

1. I will update SetPoint
2. if 1 is not working, I will uninstall it.

Here the hardware:

CPU: Intel(R) Core(TM) i7-9800X CPU @ 3.80GHz
RAM: 64 GB
Video: Radeon RX 590 Series
Disks:

• RAMDiskVE (Temp Folder)
• Samsung SSD 860 EVO 1TB (Data)
• Samsung SSD 860 EVO 2TB (NINA images)
• Samsung SSD 970 PRO 512GB (System)
• Samsung SSD 970 PRO 512GB (Program)
• WDC WD6003FZBX-00K5WB0 (Archive)

‌

[Stefan B]

I can also try to include that workaround that is posted in this topic and provide you a custom exe to test with in the next days.

At least this sounds like it could potentially be related then.

[Ruediger]

Thanks very much. This is very kind

[Stefan B]

The attached file is based on 1.11 Build 22 x64 It contains the suggested workaround that is in the linked visualstudio post. Backup your old exe and replace it with this one and let's check if this prevents this problem

[Ruediger]

Thanks! Downloaded and installed. I will run longer test tomorrow, since it is quite late here GMT+1.
So far looks good. Can start it and load the profiles.

Also updated Logitech.

Again: Many thanks!

[Ruediger]

Quick run: Two complete sequences passed without hick up. Long runs will follow tomorrow

[Ruediger]

Hi Stefan,
after 10 hours running a looping sequence with hundreds of exposures (ASCOM simulators) there was not a single exception displayed. Neither with manual interaction, nor running untended. It looks like that this version is much more robust.

Should I see in the log any indication that the culprit exception occurred again, but was captured by the added code?

Of course, this is not a prove of evidence, but it seems something has improved. This is the longest time NINA ever ran. Is it possible to add this fix to normal development branch? Or does it impact other users?

Thank you!

Ruediger

‌

[Stefan B]

That sounds promising

I haven’t put in any log to identify if that issue ocurred, however putting that piece of code into the main code line is not a problem at all and i will do so for the next nightly. Hopefully this is fixed now with that workaround! What an annoying problem!

‌

[Stefan B]

putting it to resolved with fingers crossed.

If the problem happens again, please reopen for further investigation.

[Ruediger]

That’s fine. NINA ist still running wo crash. I also keep my fingers crossed, but it looks really promising.

If I got i it right, I can continue to update to the next nightly since they contain this work around onwards. Right?

Cheers Rüdiger

[Stefan B]

Yes Nightly 23 has this workaround included

[Ruediger]

Hi Stefan,

I did a 14 hour session with NINA .24 and a complex sequence with two target was successfully processed unattended and no exception occurred. It looks like the problem got solved by the fix.

Thanks again!

Rüdiger

‌

[Stefan B]

Glad to hear!

[Ruediger]

Hi Stefan,

we can consider the problem to be solved in fact. I had a 48 hours continuous run without a single exception. The bug is crushed
Many thanks for your support.

Cheers
Rüdiger

‌

[Stefan B]

Thank you for the feedback. Really looks like this was the root cause and some bug in the WPF framework. Gladly this could be worked around.

[Ruediger]

Thanks a lot for all your efforts.
Just got reply from my Baader contact. They will forward the link to the SW developer in expectations they will also read and follow the updates here.

[Stefan B]

Removing version: 1.11 Nightly (automated comment)