Use Windows Start > Accessories > Command Prompt to open the console, then
1. Adjust the Layout properties of the console to ensure a large Screen Buffer Size (say, several hundred for the Height).
2. CD to the ...\sqldeveloper\sqldeveloper\bin directory of the folder where you unzipped SQL Developer.
3. Run sqldeveloper.exe from the console
Thanks for the reply, Gary. I set the screen buffer width to 100 and the height to 900. Changed directories to the sql developer bin directory and run from the console. After Sql Developer ends, I do Ctrl + Break in the command screen. Here is the output (there is not much):
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
LOAD TIME : 390UsersCache.fillIn() time = 528 ret==null?: false
Ctrl+Break only produces a thread dump from the Java VM while Java is running. After it closes -- nothing.
You mentioned debug mode. I take it that means you changed the sqldeveloper.conf file so that the line
Since you are getting nothing, however, it strikes me the next place to look would be the logs in Windows Event Viewer, or perhaps get guidance from the vendor of your VDI.
Thanks again, Gary. I'll check with the VDI vendor.
Good chance there's a Windows DLL or device driver that's causing the JVM to 'wigout' - hopefully you'd see that in the cmd window next time SQLDev closes unexpectedly