Bug 322249 (MONO79543) - Parsing of compiler output very slow
Summary: Parsing of compiler output very slow
Status: RESOLVED MOVED
Alias: MONO79543
Product: MonoDevelop
Classification: Mono
Component: general (show other bugs)
Version: 0.10
Hardware: Other Debian Woody
: P3 - Medium : Minor
Target Milestone: ---
Assignee: MD Bugs
QA Contact: MD Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-01 14:03 UTC by Andre Offringa
Modified: 2007-09-15 21:23 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Wiest 2007-09-15 20:11:38 UTC


---- Reported by andre@fmf.nl 2006-10-01 07:03:23 MST ----

Description of Problem: After compiling, if there are errors or warnings,
the compiler output is parsed and the errors/warning are shown in the
Errors/warnings dialog. However, if there are many errors (say 200), it
takes about 10 seconds on my 2,4ghz computer before the tabview switches
from compiler output switches to the error/warnings tab (while the compile
itself takes less than 1 second). I think this is not necessary and due to
a bug.

Steps to reproduce the problem:
1. Make sure to have a sourcefile with about 200 errors/warning (try to
convert a reasonable java file to C# e.g.)
2. Compile it

Actual Results:
After compile finished, it takes quite long to switch to the errors/warning
tab and the processor is working at 100% for some time.

Expected Results:
The errors/warnings tab shows immediatly after compiling.

How often does this happen? 
Always if there are many errors.

Additional Information:
-



---- Additional Comments From andre@fmf.nl 2006-10-02 05:39:43 MST ----



*** This bug has been marked as a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=MONO79360 ***


This bug was marked DUPLICATE in the database it was moved from.
    Changing resolution to "MOVED"