This content has been marked as final. Show 3 replies
Might there be a java.lang.OutOfMemoryError anywhere in the stack trace? That would explain the unresponsiveness and even possibly the 100% CPU issue (if OutOfMemory not on main thread). The CPU being pegged could be due to some never-ending Java garbage collection.
If the product has been open for an extended period of time, then memory leaks or just having lots of connections/panes open may be the problem's source, whether or not there is an actual OutOfMemoryError.
SQL Developer Team
My comment about memory leaks/over-utilization being an underlying cause may still be valid. Comparing the value of
AddVMOption -Xmx640M //in your SQL Developer installation's ide.conf filewith the sqldeveloper memory usage shown in something like Windows Task Manager, a value greater than or equal to the Xmx value coupled with 100% CPU can point to garbage collection gone wild...