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 71647 - Crash during startup destroys display
Summary: Crash during startup destroys display
Status: RESOLVED INVALID
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-20 10:23 UTC by kitfox
Modified: 2006-01-20 19:21 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
log file (570.59 KB, text/plain)
2006-01-20 10:25 UTC, kitfox
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kitfox 2006-01-20 10:23:32 UTC
This is the second time this has happened to me.  In this last occurrence, I
made a change to a library that my module depends on.  I compiled my jar, cut
and paste the jar into the right place in the suite, and recompiled my linked
module library.  However, I neglected to recompile my main module, which had
compiled classes that now called functions in my library that no longer existed.  

I ran my module, and it crashed during startup, issuing a 'method not found'
exception.  I fixed the problem, and recomplied.  However, now whenever I try to
run my module, all that appears is a JFrame with no content.  The messages
printed to stderr during startup are different too.  I've cleaned and rebuilt,
but only the empty JFrame appears when I run now.

How can I restore my module to normal working order?  The last time this
happened, I had to abandon my module and start a new one.
Comment 1 kitfox 2006-01-20 10:25:40 UTC
Created attachment 28489 [details]
log file
Comment 2 Petr Nejedly 2006-01-20 11:15:24 UTC
I'd suggest to clean up your userdir.
Reassigning.
Comment 3 Jesse Glick 2006-01-20 19:21:10 UTC
Make sure you have deleted the user dir when you do a clean. Other than that
there's not much to say, without steps to reproduce or some reporter-side
investigation of the root problem. A dirty user dir is most likely.