|
Ludek
2022-09-08 14:26
developer
~0069183
Last edited: 2022-09-08 15:04
|
I can't replicate (Petr & Michal also can't), but based on the logs it is the finalization of Eureka itself that doesn't like disconnection from the network for some reason in your environment.
Could you please do more tests to confirm whether:
1) Does it always happens with 5.0.4.2661 debug ?
3) Which actions are made after the start and before closing?
4) Happens with 5.0.3 non-debug ?
5) Happens with 5.0.3. debug?
and submit the crash logs?
Thanks!
|
|
|
|
Couple of note, some might be unrelated and could be split to another issue if needed:
1. I could reproduce randomly twice. Didn't seem to occur directly while offline, both cases actually occurred a short while _after_ I got back online (but this might be just a random thing). I tried to send debug logs, but not sure whether the correct ones got through, as before I confirmed the first crashreport, another appeared preventing me to send the original one.
2. (possible related?) While testing, I found out that I can quite easily start MM5 multiple timed, even though it's disabled in options. The easiest steps to reproduce are:
a. Open and close MM.
b. Right after the previous step, try to start MM multiple times => There's a small delay (while the previous instance closes), but then >1 instance shows.
Note, that in some cases, I was able to start multiple instances even without the specific timing described above.
3. (possible related?) The cookie consent can appear _behind_ the main window making look MM5 stuck. This is probably caused by the fact that the main window itself isn't in the foreground (started from FAR and FAR itself stayed in the foreground).
I wonder, maybe with could delay the consent dialog e.g. 1 minute after MM5 start and only when MM5 is the topmost/active window? This way it wouldn't be that distracting right after MM5 start and hopefully wouldn't appear behind the MM5 window. |
|
|
Ludek
2022-09-09 12:50
developer
~0069189
Last edited: 2022-09-09 12:58
|
1. Yes, Jiri's log 85280000 looks exactly like Jordan's AD2A0000 and it is the finalization of Eureka itself that crashes for some reason.
i.e. probably happens only with debug builds?
2. Seems for Petr to look into it.
3. Seems for Michal -- assuming Jiri means the new Google Cookies dialog shown in EU -- due to artwork search functionality?
|
|
|
|
1. This seems to be the second crash log then (i.e. useless, as it doesn't show the original cause). Today I tried many times, but couldn't reproduce. In the end, I got a crash during a rapid MM start/shutdown. Not sure whether it's the same issue, but managed the send the first (i.e. correct) crash log.
3. It also seems that the creation of the Consent dialog switches MM to a stay-on-top mode, which doesn't stop even when the dialog is closed. All other apps are shown _behind_ MM5 then. |
|
|
|
3) fixed |
|
|
|
Fixed |
|
|
|
3) Verified 2825 |
|
|
|
Re verified 2832 and 3000
Unable to replicate anymore |
|
