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.
Summary: | IOException after restart of IDE | ||
---|---|---|---|
Product: | platform | Reporter: | Lukas Hasik <lhasik> |
Component: | Window System | Assignee: | David Simonek <dsimonek> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | akemr, vstejskal |
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
ide.log with exception
Exception stack trace |
Description
Lukas Hasik
2001-09-20 14:50:26 UTC
Created attachment 2622 [details]
ide.log with exception
Dafe, maybe it's duplicate or it has something to do with this issue http://www.netbeans.org/issues/show_bug.cgi?id=15440 at least the exception is same... Adding Ales, many eyes see more :-) *** Issue 15440 has been marked as a duplicate of this issue. *** I think that I can reproduce the same IOE just by executing ant script as first action after IDE restart. Working with build 20010921. Created attachment 2647 [details]
Exception stack trace
maybe you noticed it but ... The exception appears when OW is opened. If you try the scenario and as "step 4.5 - close OW" then the exception appears (after restart) when View->Output window is selected or when you compile... well when OW opens :) this exception appears also when switching from SDI to MDI see issue 15967 *** Issue 15921 has been marked as a duplicate of this issue. *** Vita, part of issue 15758 is duplicate of this issue, please check scenarios that are mentioned here. Thanks! Unwanted tabs in OutputWindow are not serialized anymore. Exceptions disappeared, but the behavior of OW is still not good IMO, beacuse it persists only when the Output tab was opened. That's why the OW isn't displayed after the step 5. in original report. This is bug in OW, I guess. Fixed in main trunk. *** Issue 16142 has been marked as a duplicate of this issue. *** verified - this problem is gone for long time ;) Resolved for 3.4.x or earlier, no new info since then -> closing. |