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 216167 - Convert output window to BigByteBuffer / MappedBigByteBuffer
Summary: Convert output window to BigByteBuffer / MappedBigByteBuffer
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: Output Window (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal (vote)
Assignee: Jaroslav Havlin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-31 07:35 UTC by _ tboudreau
Modified: 2012-07-31 15:48 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ tboudreau 2012-07-31 07:35:13 UTC
I never really liked the fact that the output window is limited in length to Integer.MAX_VALUE / 2.  With JDK 7's BigByteBuffer and MappedBigByteBuffer, it does not have to be.

Probably necessary to stop line wrapping at Integer.MAX_VALUE unless somebody wants to create a long-indexable int:int map, though.
Comment 1 Jaroslav Havlin 2012-07-31 15:48:20 UTC
The limit causes a lot of problems, and this would help. Thanks for hint.

We are also considering decreasing the limit and keeping only several thousands last lines. Or storing all lines (that can be accessed after "Save as"), but showing only several thousands last lines. See issue 55151.

Keeping smaller number of lines could also help solve some other issues, like IO from AWT (issue 183009), and maybe some rendering problems (overlapping lines).

Please, what is your use-case for keeping such a huge output in Output Window?
Could you list pros and cons of limited and unlimited output, from your point of view?
Thank you.

P.S. I really admire your work on Output Window.