If you found a bug post here your report.
Unhandled Exception of SyMenu
|
chef Posts: 47
23/07/2019
|
This crash happened the first time. It entered a strange mode with two windows when I entered the settings menu, keeping two windows instead of turning to one window with the settings form. The other window was the submenu to enter the settings form.
Even when finishing a configuration setting session and closing that settings form normally, the other window remained some time and then turned into that unhandled exception reported by SyMenu in the non-resizeable window which you may find in the attached screenshot  .
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
24/07/2019
|
I tried to reproduce this problem but it's difficult without knowing the exact procedure you followed.
Anyway when the things become strange, it's quite normal that a bug can appear. The important thing is that the bugs are not here when you work normally.
|
|
|
link
|
|
chef Posts: 47
24/07/2019
|
No, it's the other way round.
The situation reported that the 2nd window remained is a consequence of a present bug in SyMenu. Difficulties in reproducing are a hint on probably dynamic race conditions still difficult to identify and reproduce. The unhandled exception comes much later on other action requiring the first bug before. And without following the advice of the exception handler, it may be difficult to identify symptom and cause which are probably different.
I worked normally and things became strange. The bugs are already present but difficult to reach. I didn't insert a bug by using SyMenu normally and nevertheless fall once on it.
This bug observed, I don't consider major nor bloquing. And if you want to say that you can't do anything on it as long as it does not get identified nor reproduced, then you're probably right too. But this doesn't mean absence of that bug.
Which advice do you want to give me?
Do you want me to follow the advice of the standard exception handler to enable debug and verbose mode in order to be prepared differently and to get not only stack trace of functions but hopefully also of paramenters, hoping it will not impact too much normal behaviour and focus only on unhandled exceptions?
I don't know if I saved a copy of the instruction to enable this mode. I'm sure I didn't save it yesterday. But I remember having seen and reported unhandled exceptions on different bug already before and assume having saved also that instruction then.
An independant hint on bugs. Microsoft did break compatibility with its functional update of Windows 10 of this spring. At least some driver publishers and anti-virus publishers were concerned. I don't expect SyMenu to be concerned. So such context changes may change the probability the already present bugs get observed or not. And this has nothing to do if users work normally or not. For this type of change, it's not users operation nor mode, it's the operating system context which may have changed. And Microsoft has rolled out this spring update an my tablet but not yet on my notebook. On my tablet, I don't have SyMenu installed. On my notebook, I've SyMenu installed but Microsoft warns me not to update Windows with that functional update neither by Windows update nor by reinstalling Windows, and will keep me informed when I may consider updateing in the future after they fixed further issues and some cooperating partners too.
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
25/07/2019
|
What I can understand from the exception you posted, not so much because I don't speak German, it's useless to investigate further in it.
It seems a wrong disposition operation on an object (the menu itself) that shouldn't be disposed because it needs to be active all along the application lifetime.
Usually the reasons for this kind of problems are not highlighted in the stack trace and it's very difficult to find out them in debug mode too.
The only hope is that the problem can be reproduce with a defined actions sequence so that I can understand the real reason. Until that moment, please try to ignore the error if it is not so annoying or blocking.
|
|
|
link
|