Change in resolution causes crash

Asked by Hans Jansen on 2020-06-08

I ran the script on a widescreen monitor 2560x1080 and the scripts executes correctly
Close the IDE, and then changed monitors to a 1920x1080 monitor, and the IDE does not want to start up. It freezes while it shows IDE starting on Java8.
There is no way to restart the IDE but to use the widescreen monitor again at 2560x1080 in which case the IDE starts up correctly.

A way around I found, is to connect the widescreen monitor, in which case the IDE will start up, at which stage I can switch the monitor while the IDE is running.. The crash seems to have something to do with startup that did not like the resolution switch.

My question is what is the temporary files I can delete that checks what the previous resolution the IDE was running in because I only had the widescreen monitor on my test pc for a short time

Question information

English Edit question
Sikuli Edit question
No assignee Edit question
Solved by:
Last query:
Last reply:
Best RaiMan (raimund-hocke) said : #1

I think it is a problem with the restore of the IDE window from the last run (position and/or size does not fit).

You can try to delete the SikuliX session store from the registry using regedit:

Hope it helps.

Hans Jansen (whitemagick) said : #2

That worked perfectly!

I must say that I am in love with this project and I am very surprised by the quick and accurate answer. This is by far my favorite testing tool, and I find I am using it more and more frequently for automation and testing.

I think it was the IDE size that could not load at the larger size of IDE unto the screen. It is a pity that it loses all the open projects I had (but I just have to re-open them), but I am so relieved that I can use that machine again for testing.

Thank you again for the quick and accurate response. I hope to contribute in the future to this project in one way or the other.

Hans Jansen (whitemagick) said : #3

Thanks RaiMan, that solved my question.

RaiMan (raimund-hocke) said : #4

Thanks for kind feedback.

Your case is on the list now, to get improved by implementing a more robust behavior.