JDK-6713352 : Deadlock in JFileChooser with synchronized custom FileSystemView
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version:
    2.0.3.10,2.0.3.13,3.0_sp9,6,6u5,6u10,6u14 2.0.3.10,2.0.3.13,3.0_sp9,6,6u5,6u10,6u14
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS:
    generic,linux_2.4,linux_redhat_6.0,solaris_10,windows,windows_xp,windows_vista generic,linux_2.4,linux_redhat_6.0,solaris_10,windows,windows_xp,windows_vista
  • CPU: generic,other,unknown,x86
  • Submitted: 2008-06-11
  • Updated: 2024-03-04
  • Resolved: 2009-12-30
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other JDK 6 JDK 7
5.0-poolResolved 6u17-revFixed 7 b60Fixed
Related Reports
Duplicate :  
JDK-6741890 - Deadlock in Win32ShellFolderManager2
Duplicate :  
JDK-6857569 - JFileChooser hangs on Windows XP when CrossPlatformLookAndFeel is used
Duplicate :  
JDK-6756220 - JFileChooser blocks AWT-EventQueue-0 when user clicks 'Up One Level' button
Duplicate :  
JDK-6744953 - JFileChooser deadlock when shown after UI update and rescan
Duplicate :  
JDK-6789084 - Deadlock when trying to bring up the JFileChooser
Relates :  
JDK-6940843 - FileSystemView.isFileSystemRoot causing various exceptions under 6u19
Relates :  
JDK-8324973 - Replace Vector with ArrayList in BasicDirectoryModel.FilesLoader
Relates :  
JDK-2191861 - The Win32ShellFolderManager2.isFileSystemRoot can throw NPE
Relates :  
JDK-6892340 - Part of the CR 6741890 should be forwardported
Relates :  
JDK-6845805 - Test for CR 6713352 is failed under Linux
Relates :  
JDK-8327234 - In File Loading Thread filechooser.isTraversable is run on COM thread
Relates :  
CODETOOLS-6712619 - Customized FileChooser (Open TS, WD, Report) dialogs are not compatible with JDK 6_u4 and later
Relates :  
JDK-6923226 - Exceptions at running JavaTest GUI
Description
If a custom implementation of FileSystemView forwarding any calls to the COM thread from its synchronized methods, is set, it causes a deadlock.
_
Comments
WORK AROUND Almost all Win32ShellFolder2 methods can produce deadlock. E.g. listFiles, getDisplayName, getFolderType, isFileSystem, isDirectory isHidden and many other.
01-06-2009
EVALUATION ComThread should be used ONLY in our classes. We should avoid invocation of external code (like FileSystemView implementation) from ComThread. The fix of this CR is moving invocations of FileSystemView from ComThread to another thread. I also fixed here synchronized methods in Win32ShellFolder2, because it's another cause of deadlock.
15-05-2009
EVALUATION Synchronized methods of the custom FileSystemView can be invoked from both EDT and COM threads. Logically, it's the single control flow, but from the security subsystem's point of view, it's not allowed to enter a synchronized method from the COM thread till another synchronized method invoked from the EDT, is finished.
11-06-2008
WORK AROUND Avoid invocation of Win32ShellFolder2's methods forwarding their execution to the COM thread, from within custom FileSystemView's synchronized methods. For example, use getAbsolutePath() instead of getAbsoluteFile().
11-06-2008