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 17782 - First startup, enabling MINIMAL modules causes Netbeans to freeze at startup.
Summary: First startup, enabling MINIMAL modules causes Netbeans to freeze at startup.
Status: CLOSED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Windows 3.1/NT
: P1 blocker (vote)
Assignee: issues@platform
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-16 16:22 UTC by rsk
Modified: 2008-12-22 21:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Log file from IDE startup before its death (3.78 KB, text/plain)
2001-11-16 16:23 UTC, rsk
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rsk 2001-11-16 16:22:45 UTC
SYSTEM:
Windows XP
JDK 1.3.1_01
Netbeans 3.3 Beta 4

PROBLEM:
On the initial run of Beta 4 when presented with all the configuration 
options, I went on to the modules menu and ENABLED the following modules (by 
ENABLING only these modules, it means that EVERY OTHER MODULE was disabled, 
and yes, that's quite a few, but nothing critical).

Data Files
	Text
Editing
	Editor
Infrastructure
	Auto Update
	Projects
	User Utilities
Java
	Java Source Files
	Javadoc
Web
	HTML
Libraries
	<Everything, since I can't shut it off>

Then after hitting "finish", netbeans promptly decided to freeze and 
completely lock up. The ONLY thing that happened was that the splash screen 
came up, then the title bar drew itself (in SDI mode, even though I selected 
MDI mode) but crashed before it got a chance to paint. So the only thing I 
have on my screen is a gray title bar (the bar across the top that has all the 
form editor widgets and compile buttons and menubar and what not) and a splash 
screen, that won't repaint when I move a window over it (e.g. hard locked).

I will attach my ide.log so you can better determine where the startup died.
Comment 1 rsk 2001-11-16 16:23:59 UTC
Created attachment 3456 [details]
Log file from IDE startup before its death
Comment 2 Jesse Glick 2001-11-17 10:12:00 UTC
I can't reproduce any deadlock in [dev nov 17] on Linux. I started a
build with a fresh userdir, turned off all the modules you say, hit
Finish in the Setup Wizard, and the main window opened, it chewed away
for twenty seconds or so turning off modules, and then was fine. A few
harmless exceptions from the window system on the console, but no
deadlock.

If this is reproducible for you, next time include a thread dump. An
ide.log file is not enough in case of a deadlock, we need a full
thread dump (Ctrl-Break on windows).
Comment 3 Quality Engineering 2003-07-01 15:58:04 UTC
Resolved for 3.4.x or earlier, no new info since then -> verified.

Comment 4 Quality Engineering 2003-07-01 16:38:53 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.