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 162777 - Can't start netbeans.
Summary: Can't start netbeans.
Status: RESOLVED DUPLICATE of bug 161691
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: mslama
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-16 03:15 UTC by wgiffin
Modified: 2009-04-28 11:08 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
log file (38.54 KB, text/plain)
2009-04-16 03:17 UTC, wgiffin
Details
thread dump - as requested! (8.37 KB, text/plain)
2009-04-17 02:02 UTC, wgiffin
Details
another thread dump - CPU use 0-2%, no unusual memory use (9.59 KB, text/plain)
2009-04-18 02:02 UTC, wgiffin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description wgiffin 2009-04-16 03:15:09 UTC
Progress bar makes it to "starting modules" but won't complete.  If another Java app is running, however, netbeans 
will start.   Once it starts it will continue to work properly until operating system restart then it won't start 
again.
Comment 1 wgiffin 2009-04-16 03:17:11 UTC
Created attachment 80206 [details]
log file
Comment 2 mslama 2009-04-16 10:02:57 UTC
Need thread dump to see where it hangs.
Comment 4 wgiffin 2009-04-17 02:02:59 UTC
Created attachment 80303 [details]
thread dump - as requested!
Comment 5 mslama 2009-04-17 12:39:46 UTC
There is no deadlock. Thread 'main' is runnable. Please attach more thread dumps say 4 periodically after 10s, 30s, 1min
to see what happens if there is any change or if it stays the same.
Comment 6 mslama 2009-04-17 12:41:14 UTC
Also is there any disk activity or CPU usage?
Comment 7 wgiffin 2009-04-18 02:02:54 UTC
Created attachment 80394 [details]
another thread dump - CPU use 0-2%, no unusual memory use
Comment 8 wgiffin 2009-04-28 01:56:27 UTC
Issue resolved.  User inadvertently activated ui gesture logging - but primarily works off the net.  Netbeans tries to 
submit data to server, fails and writes an error message in the user's Temp directory.  More than 30 MILLION of these 
message files accumulated in the temp directory, which, Netbeans apparantly scans at startup.  This is what caused the 
20+ minute delay and possible the heap allocation errors as well.   Strongly recommend only entering one error log 
message per day, informing the user and allowing them to disable UI gesture logging, warning them if there is too much 
stuff in the Temp directory, or some other manner to coach the user out of this unfortunate circumstance.
Comment 9 mslama 2009-04-28 11:00:17 UTC
It was bug. Already reported and fixed.

*** This issue has been marked as a duplicate of 161691 ***
Comment 10 mslama 2009-04-28 11:08:17 UTC
Workaround is to disable 'UI Gesture Collector' to avoid generating many temp files and clean content of temp directory
to fix long start. (In this case profiler tries to list content of temp dir and delete its temporary files. When there
is a lot of file in temp dir it can take long.) Also it might be necessary to disable 'Usage Statistics' at Tools ->
Options -> General tab - uncheck checkbox "Help us to improve ..." at bottom of dialog.