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 12925 - Exception dialog: Next button takes too long
Summary: Exception dialog: Next button takes too long
Status: CLOSED DUPLICATE of bug 16491
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: akemr
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2001-06-17 01:02 UTC by Jesse Glick
Modified: 2008-12-22 22:56 UTC (History)
2 users (show)

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 Jesse Glick 2001-06-17 01:02:23 UTC 
[dev jun 15] Exception dialog: takes a full second to show next exception when
you click Next-> (small stack traces). In the meantime it looks blank (not sure
if AWT thread is hung during this time, I think not). I do not believe it used
to take this long, and it is certainly not reasonable. 1.3.0 on Linux.
Comment 1 Jesse Glick 2001-11-01 11:46:52 UTC 
Still broken BTW, someone should run a profiler here.
Comment 2 Peter Zavadsky 2001-11-14 17:07:50 UTC 
This is just evaluation.
The problem is in org/netbeans/core/output/OutPane.java
Look at the code around line 375. The repainting si always ignored until  
almost 1 sec has expired since the prevoius one.

I don't know why is there such painting policy, it was added by 1.60
revision by Ales, and he is not here anymore.
Comment 3 Jesse Glick 2001-11-15 11:13:00 UTC 
I remember anovak doing various fixes to the Output Window for
performance, designed for ten-thousand-line outputs. However now that
term is in use for such things, OutPane is used for nothing AFAIK
except the exception window. Probably we should either:

1. Delete it entirely and convert the exception dialog to use term.

or

2. Remove all the complicated old performance code which actually
hurts when you have only a few lines as is now typical.

I guess I would prefer 1.; at least it means a few fewer classes
loaded from core, and one less GUI component that needs to be kept
accessible etc....
Comment 4 akemr 2001-11-15 11:22:31 UTC 
I have already reported bug to remove OutPane.. #16491,
so I'm closing this as DUPLICATE

*** This issue has been marked as a duplicate of 16491 ***
Comment 5 Quality Engineering 2003-07-01 15:59:31 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verified.
Comment 6 Quality Engineering 2003-07-01 16:47:23 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.