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: | Editor is not responsive for large .sql files | ||
|---|---|---|---|
| Product: | editor | Reporter: | Petr Jiricka <pjiricka> |
| Component: | Painting & Printing | Assignee: | issues@editor <issues> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | blocker | CC: | abadea, romanmostyka |
| Priority: | P3 | Keywords: | PERFORMANCE |
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Bug Depends on: | 121357 | ||
| Bug Blocks: | |||
| Attachments: |
Thread dump
Attaching the file in a zip file. The longest line in the file is >200,000 characters. |
||
|
Description
Petr Jiricka
2008-06-05 10:47:48 UTC
Created attachment 62410 [details]
Thread dump
All thread dumps I took show the editor being busy drawing. By the way, the file I and the reporter tested with has very long lines, perhaps that could be the cause. The new view hierarchy will hopefully perform better. How long lines are we talking? Could you attach sakila-data.sql here (perhaps in a .zip form)? Thanks Created attachment 62528 [details]
Attaching the file in a zip file. The longest line in the file is >200,000 characters.
Oh well, that's it then. I opened sakila-data.sql and although the editor was sluggish it seemed to handle the file quite well. The longest line I found was 1.032.623 characters long. I pasted it to OpenOffice and it created 338 pages of text, the number of characters is from the document statistics. GEdit didn't even render a line like this for example. Anyway, the editor with current view hierarchy can handle seamlessly lines with ~100k characters (see issue #114016), which IMO is beyond any practical use. The new hierarchy should perform even better, but the task hasn't made it to any schedule yet. |