Chrome + Java = Potential Memory Problems

[Glitchless]

We've been mentioning for a while now that we've seen some issues with Chrome and Java. Chrome is often leaving extra instances of java.exe running when it fails to interface properly with Java during initialization, or even when a browser window is closed. Chrome users have likely learned to just ignore this, and try again, opening a new window, but after a while those extra java.exe's running in the background eat up your system memory, causing you to swap (i.e. use your hard drive as RAM, which causes tons of performance problems).

For Windows OS Chrome users, we suggest you use the CTRL-ALT-DEL key combo to bring up the task manager, and double check under Processes to make sure you don't have a bunch of java.exe's listed under the Image Name column. If so, you should restart your computer to free up your system memory. You should only have 1 java.exe per Nodiatis window.

We've switched to Firefox as our browser of choice for running Nodiatis for the time being. You may wish to as well. Note that if you are unable to hear sounds, that is an IE 11 issue (or you don't have Flash installed) which may prompt you to wish to change to Firefox as well.

[Claudia]

Well, i was unaware of the problem with chrome, but i did notice in the task manager double the java.exe that actual nod tabs i had, i always and still do this, end the processes and usually works for me. Dont know if its the right thing to do but it works for me with chrome, and i would like to believe thet it is something that can be fixed, since my personal preference is chrome.

Thanks for the warning and have fun with nod in which ever browser makes it work for ya