[ideTestRunner] Product Version = NetBeans IDE Dev (Build 200804271202)
[ideTestRunner] Operating System = Windows XP version 5.1 running on x86
[ideTestRunner] Java; VM; Vendor = 1.6.0_04; Java HotSpot(TM) Client VM 10.0-b19; Sun Microsystems Inc.
Performance test went into a freeze on finishing New Project wizard for mobility project.
Created attachment 60732 [details]
Created attachment 60733 [details]
Created attachment 60734 [details]
Could you provide the way to run this test?
This is not a performance bug
I have run into this issue as well, during testing of fixes for issue 147403.
The fix for issue 147403 changes the call sequence and threading when a new project is created (by taking sample midlet creation off the event thread). With
no locks possibly being held when the sample midlet is created (it is now done in a background thread).
In the attached thread dump, the AWT thread is blocked inside org.netbeans.modules.mobility.project.J2MEProjectGenerator$4.doPostGeneration(), which
creates the sample midlet. So it is very likely that the fix for issue 147403 (I have attached a patch) will also fix this bug.
*** Issue 133218 has been marked as a duplicate of this issue. ***
To run test:
1. Get the repository and build
2. Run ant in performance dir
3. Unzip qa\performance\mobility\wtk252-windows.zip (or linux) from cvs repository into nbbuild\netbeans\mobility8
4. Open performance\mobility project
5. Run MeasureMobilitySetupTest to prepare environemtn
6. Run CreateMobilityProject to reproduce test
Is this reproducible after the fix for issue 147403? That fix completely changed the call order and what thread the
code that was causing the freeze-up runs on.
It looks like the fix helped