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 182350 - [69cat] Reporting an issue within the IDE while debugging ruby results in severe IDE performance problems
Summary: [69cat] Reporting an issue within the IDE while debugging ruby results in sev...
Status: RESOLVED INCOMPLETE
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Issuetracking Framework (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-19 07:57 UTC by esmithbss
Modified: 2010-03-22 15:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description esmithbss 2010-03-19 07:57:15 UTC
[ BUILD # : 201003170201 ]
[ JDK VERSION : 1.6.* ]

When you attempt to submit an issue report from the IDE while you are executing
any task in the background during ruby debugging (like running the debug
process), the IDE rapidly becomes unresponsive and pegs the CPU at 100%.
Comment 1 Tomas Stupka 2010-03-22 09:14:49 UTC
any chance to attach a thread dump
Comment 2 Tomas Stupka 2010-03-22 09:19:21 UTC
1.) and it also would be good to know what action exactly you invoked in the IDE - report an issue from the team menu report issue form the help menu, ...

2.) "while you are executing any task in the background during ruby debugging (like running the debug process)" - could you please elaborate?
Comment 3 esmithbss 2010-03-22 15:26:12 UTC
I'll try to get some thread dumps today and post them.

As for the action invoked in the IDE, that would be the "Report an Issue" item under the help menu.

And as for the "executing any task ..." I have experienced this while I was debugging my process and the IDE was:

a) scanning projects -- Identified by the label on the status bar.

b) Launching the debugger process (Determined based on timing of operations: 1) I launch my debugging process, 2) I open "Report an Issue", 3) the Report window displays, 4) The IDE locks up before the first breakpoint is hit (line 1 of my code).

c) Running Ruby Tests -- Similar to #2 but with Test and no user interaction

d) Using the Variables window to expand a large array object with the system taking time to pull in all of the details.