If document size is big and IDE asks "The file seems to be too large to safely open..." the document cannot be open by
Created attachment 89848 [details]
Created attachment 89849 [details]
another dead lock if you ansver NO on restarting IDE with openrd file
Created attachment 89853 [details]
example of application with big header "sldworks.h"
Editor team, please, evaluate.
Looks like deadlock due to thrown UserConfirmationException which is caught somewhere and trying to show dialog, but AWT
is blocked by waiting for notification of finished initialization
If you create big *.java file => the same issue - Deadlock on opening, restarting IDE with previously opened big file
Created attachment 89855 [details]
same for java
Can you attach here the messages.log file? Were there any exceptions? Thanks
Created attachment 89871 [details]
message log for first scenario
- IDE cannot be closed only be killed
- IDE cannot be opened (work around: clear user dir)
- Dialog do not have alternative (both "yes" and "no: result in IDE hanging)
- issue has 100% repeatability
So, please, remove "RANDOM" and restore priority
I can reproduce this in 6.8beta. Steps are simple:
1. start the IDE
2. open any *.java file that is larger than 1MB, confirm the dialog, let the IDE open the file in the editor
3. restart the IDE
The IDE asks the same question as in step #2, which it should not. After confirming the question by pressing 'yes' the
IDE will freeze.
Threading issues, deadlocks, regressions, etc are generally P2. If this problem is considered a showstopper for 6.8beta
we will change its priority to P1.
Data lost in unsaved editors pane is P2?
If necessary to fix for beta easy fix is to return false from overriden CloneableEditorSupport.asynchronousOpen. For
trunk I will prepare better fix. There is code to test if AWT is blocked. But if AWT is blocked by waiting on initVisual
special handling must be done - continue without need to confirm. Jarda this is more common and happen even on IDE
restart. Then UserQuestionException becomes useless because it is quite common that someone calls
CloneableEditor.getEditorPane before CE initialization is finished.
BTW what files was opened in IDE? UserQuestionException should not be thrown during IDE start. When DataEditorSupport is
used UQE is not thrown. It would be good to identify what subclass of CloneableEditorSupport does not handle it
correctly. I can also add logging to find out more. I will let you more as I will add it. Of course it does not mean
this issue should not be fixed.
this is NOT a stopper for NB 6.8 Beta : too risky and user is warned before - so she continuous on his own risk, this is
Beta not FCS ... should be solved for NB 6.8 final
"BTW what files was opened in IDE?" - Marku, this regularly happens with java files. I've also seen it with *.txt files
and cnd guys reported it with *.h files.
please, fix it in trunk like it is P1 bug.
This issue blocks our QA automatic testing (=> blocks development => should be considered as P1), but I think it is OK
not to consider as showstopper for Beta
>"BTW what files was opened in IDE?"
- configuration.xml (for huge project it can be several Mb)
Unfortunately it is another problem introduced by CloneableEditorSupport.asynchronousOpen. We will need adjust API to
support handling UQE in CloneableEditor.DoInitialize.initNonVisual. Current code does not work when we need cancel
opening (ie. user selects No in query dialog).
If we want to fix this quickly we can return false from all CloneableEditorSupport.asynchronousOpen overrides.
Fixing Yes selection and fixing blocked AWT by call of CE.getEditorPane is possible without API change. I will prepare
at least this part of fix.
Fixing No selection requires API change so we need to discuss it.
rising to P1. QA tests are blocked on projects with big documents
Integrated into 'main-golden', will be available in build *200910270201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Marek Slama <email@example.com>
Log: #175093: Fix handling of UserQuestionException.
*** Issue 175466 has been marked as a duplicate of this issue. ***
There is issue #175528 I am working on. If you are influenced by issue #175528 and need quick fix let me know. I will
change JavaEditorSupport.asynchronousOpen to false to fix this.
*** Issue 175476 has been marked as a duplicate of this issue. ***