Start a new topic

Opening a new tab causes NullPointerException

[This topic is migrated from our old forums. The original author name has been removed]

Sometimes when opening a new tab in SQL commander, a NullPointerException occurs. To reproduce, just keep hitting Ctrl+T unitl the error window pops up. Usually happens within 2-3 tries. The same error happens when starting DBVisualizer (every time, as far as I can tell). Regards, Ivan ----- An internal error occurred: java.lang.NullPointerException The error may have affected the application state. Please notify vendor. Stack Trace: java.lang.NullPointerException at sun.awt.shell.Win32ShellFolder2.pidlsEqual(Unknown Source) at sun.awt.shell.Win32ShellFolder2.equals(Unknown Source) at sun.awt.shell.Win32ShellFolderManager2.isFileSystemRoot(Unknown Source) at sun.awt.shell.ShellFolder.isFileSystemRoot(Unknown Source) at javax.swing.filechooser.FileSystemView.isFileSystemRoot(Unknown Source) at javax.swing.filechooser.WindowsFileSystemView.isTraversable(Unknown Source) at javax.swing.JFileChooser.isTraversable(Unknown Source) at javax.swing.plaf.basic.BasicDirectoryModel$LoadFilesThread.run0(Unknown Source) at javax.swing.plaf.basic.BasicDirectoryModel$LoadFilesThread.run(Unknown Source) ----- Product: DbVisualizer Personal 7.0.6 Build: #1499 (2010/04/21 08:23) Java VM: Java HotSpot(TM) Client VM Java Version: 1.6.0_20 Java Vendor: Sun Microsystems Inc. OS Name: Windows XP OS Arch: x86 OS Version: 5.1

[This reply is migrated from our old forums. The original author name has been removed]

Re: Opening a new tab causes NullPointerException
I reverted to 1.6.0_18, and everything seems OK now. Thanks. Hopefully, the guys at Oracle \[sic\] will fix this soon. :) Ivan Edited by: Ivan Habunek on Apr 21, 2010 12:43 PM
[This reply is migrated from our old forums.]

Re: Opening a new tab causes NullPointerException
Ivan, Seems as if there are some major flaws in the latest 1.6.0_19 and now also 1.6.0_20 versions of Java on Windows. Other users have reported similar problems and downgrading to 1.6.0_18 (or older) seem to solve it. Try this and keep us updated. We will most likely add a notification of this situation on our web shortly as I believe there are many users experiencing this. Best Regards Roger