>>SQL developer simply disappears/stop running.
Sounds like a video driver issue. Try updating those on your machine.
Also, run SQL Developer out of the /bin directory. That should cause a CMD windows to open alongside your sqldev GUI. When it 'crashes', you should see some sort of stack dump in the cmd window...hopefully
Indeed, a fellow Java developer coleague provided me the solution:
- #Draw performance change
- AddVMOption -Dsun.java2d.ddoffscreen=true <--change to true - default was false
- AddVMOption -Dsun.java2d.noddraw=false <-- add this line
Hopefully this swill help more people.
thatJeffSmith-Oracle despite I found solution as posted.
But following up your suggestion of starting sqldeveloper from command line it doesnt show to much information..only a LOAD TIME:
running the sqldeveloper.bat doenst work as theres no PATH for java.. but i can try if you find usefull ?
So here trying to execute the sqldeveloper.bat, i added jdk\jre\bin to PATH, but didnt started:
Im ok with the solution my java coleague provided, and marked m yreply as correct answer.
Just replying to you as I tried your suggestions, but unable to run sqldeveloper via command line and get feedback.
Congratulations! It seems that by doing this, at least in your specific environment, you not only solve the tool-tip / crash problem, but also take advantage of some acceleration / features offered by DirectDraw and Direct3D:
Edit: Which is supposedly equivalent to AddVMOption -Dsun.java2d.d3d=true
Edit2: Which, of course, is exactly the opposite of why we set ddoffscreen=false in the first place...
Intended use: To turn off the Java 2D system's use of Direct3D.
Equivalent environment variable:
How to use: On a small subset of Windows 2000 systems with buggy Direct3D drivers, the use of Direct3D can cause a system crash. To turn off the use of Direct3D, set this property to false:
>>with buggy Direct3D drivers
like i said, bad video drivers
1. The ddoffscreen and noddraw settings are obsolete since Java SE 6 Update 10 (we currently require Java 8)
2. The sqldeveloper.conf currently shipped assumes the video driver will be buggy and uses an obsolete, non-default setting.
3. The OP's video driver may or may not be buggy, but the crash occurs when using the obsolete, non-default setting.
Strangely enough, the javase/8 link I referenced in my prior post still recommends using those obsolete settings if the new default of
sun.java2d.d3d=true does not work and problems continue even when trying sun.java2d.d3d=false. Go figure!