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 25152 - runide.exe -nosplash terminates IDE
Summary: runide.exe -nosplash terminates IDE
Status: CLOSED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: _ ttran
URL:
Keywords: T9Y
Depends on:
Blocks:
 
Reported: 2002-06-25 18:07 UTC by L Martinek
Modified: 2008-12-22 22:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description L Martinek 2002-06-25 18:07:31 UTC 
Run runide.exe with argument "-nosplash" and IDE
will start and then immediately exit. This affects
our testing infrastructure.
Comment 1 _ ttran 2002-06-26 07:09:32 UTC 
please don't forget to mark bugs which affect testability with the T9Y
keyword
Comment 2 _ ttran 2002-06-26 08:49:52 UTC 
No way for me to reproduce the bug with the latest dev build.  I've
also looked at the code and saw no apparent defect which would cause
the IDE to shutdown.

If you're able to reproduce this bug, please tell me the build number,
JDK, OS version.  As much info as possible.  Thanks
Comment 3 L Martinek 2002-06-26 10:11:53 UTC 
It happens only on jdk1.3. On last build (200206260100) I also had to
add netbeans.full.hack=true to reproduce it. Checked on Windows 2000
and Solaris 8. So command line look like this:
"runide.exe -jdkhome c:\java\jdk1.3.1 -nosplash
-J-Dnetbeans.full.hack=true"
Comment 4 _ ttran 2002-06-26 15:47:12 UTC 
jdk 1.3?  I see.  It happens on my Linux with jdk 1.3.1_03 too.  It
works fine with Blackdown JDK.  I'll try to investigate further but
it's very likely that something is wrong in the JDK not NB code
Comment 5 _ ttran 2002-06-27 15:25:21 UTC 
I've checked all the relevant code and saw no suspects.  System.exit()
certainly is not called at all.  Some piece of native code terminates
the process.  Looks like it happens at the moment when we want to show
an AWT window.

No chance to fix this bug.  If you need to run tests on jdk 1.3 try
not using -nosplash
Comment 6 Quality Engineering 2003-07-01 15:51:30 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verified.
Comment 7 Quality Engineering 2003-07-01 16:30:44 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.