This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 206049

Summary: Deadlock when opening a project created by newer version
Product: cnd Reporter: Vladimir Kvashin <vkvashin>
Component: ProjectAssignee: igor_nikiforov <igor_nikiforov>
Status: RESOLVED FIXED    
Severity: normal CC: tbrunhoff
Priority: P2    
Version: 6.x   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter:
Attachments: Full thread dump

Description Vladimir Kvashin 2011-12-07 07:39:43 UTC
Created attachment 113903 [details]
Full thread dump

On IDE startup it tried to open previously opened projects. 
But before restarting IDE, I opened one of these projects with a newer NB version.
So on restart, a warning appeared "The project was created with a newer version...". At that moment UI froze forever.
This occurs 100% stable (with my userdir at least)
Comment 1 Leonid Lenyashin 2011-12-07 14:13:55 UTC
All post cut-off P2s must be evaluated for show-stopper status.
Please evaluate.
Comment 2 igor_nikiforov 2012-01-16 09:48:48 UTC
The workaround for this issue is the following:
  1. Close frozen IDE, by killing it's java process.
  2. Rename project with newer version.
  3. Open IDE.
  4. Restore previous project name.
  5. Open project from the IDE.

This issue is quite long with us and workaround existing, so I don't think it should go to patch.
Comment 3 igor_nikiforov 2012-01-31 14:32:48 UTC
The issue is resolved. In addition the Project View project node context menu item ("Resolve project version problem...") is added which is available only if project version is unsupported and allows to open it anyway.

The notification dialog is shown as it was later.

The fix is here:
  http://hg.netbeans.org/cnd-main/rev/d61ab7b3d6c8
Comment 4 igor_nikiforov 2012-01-31 15:46:00 UTC
More fixes:
  http://hg.netbeans.org/cnd-main/rev/350f0f522bb0
Comment 5 igor_nikiforov 2012-03-23 06:43:11 UTC
*** Bug 209967 has been marked as a duplicate of this bug. ***