by Barry4679 » Thu Nov 26, 2020 11:44 pm
Ludek wrote: ↑Thu Nov 26, 2020 12:41 pm
Are you sure that removing persistent.json did the trick?
But please send me the affected persistent.json (in case you are still seeing the issue when you replace it back over your re-newed json).
OK, I sent it.
I stopped MM5, and then restored the json, and then restarted MM5 ... it did not immediately exhibit the hover problem.
But then I closed MM5, and restarted it again, and I have the persistent hover problem again.
It seems repeatable to me ... ie. did the above procedure twice ... with a gap between, where I allowed MM5 to build a new json file, and which resulted in no hover problem .... but the two separate sessions, with the "problem" json file, exhibit the hover problem.
Once MM5 is in this state, I get no hover tool tips, even if I leave MM5 alone a while to settle after re-starting. ... I can fix this persistent state by deleting the json file.
I also sent you a second json file ... this one throws MM5 in a "reading files" state, that eventually leads to a
variety of crashes ... all these from today, using that 2nd json file.... again this problem is fixed by closing MM5 and deleting the json file.
The "Last Known" crash is what happens if I use your "restart" button on the crash dbox panels ... that has never worked for me, and I have seen others say the same thing ... you should remove that button if you cannot fix it. ... in the current state it just adds frustration to frustration
[quote=Ludek post_id=475082 time=1606412479 user_id=7319]
Are you sure that removing persistent.json did the trick?
But please send me the affected persistent.json (in case you are still seeing the issue when you replace it back over your re-newed json).
[/quote]
OK, I sent it.
I stopped MM5, and then restored the json, and then restarted MM5 ... it did not immediately exhibit the hover problem.
But then I closed MM5, and restarted it again, and I have the persistent hover problem again.
It seems repeatable to me ... ie. did the above procedure twice ... with a gap between, where I allowed MM5 to build a new json file, and which resulted in no hover problem .... but the two separate sessions, with the "problem" json file, exhibit the hover problem.
Once MM5 is in this state, I get no hover tool tips, even if I leave MM5 alone a while to settle after re-starting. ... I can fix this persistent state by deleting the json file.
I also sent you a second json file ... this one throws MM5 in a "reading files" state, that eventually leads to a [url=https://www.dropbox.com/s/cww64109od4tqpr/json%20related%20crashes.png?dl=0]variety of crashes[/url] ... all these from today, using that 2nd json file.... again this problem is fixed by closing MM5 and deleting the json file.
The "Last Known" crash is what happens if I use your "restart" button on the crash dbox panels ... that has never worked for me, and I have seen others say the same thing ... you should remove that button if you cannot fix it. ... in the current state it just adds frustration to frustration