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.
When scrolling down Java source files where (on my system) the file has more than 1927 lines the source text becomes garbled. It does not appear to be directly related to memory as the garbling does not occur no matter how many characters are inserted on the 1927th line. The line the cursor is on is displayed correctly. This occurs using Linux but not in Windows. Linux Kernel: 2.6.25 X.Org X Server 1.4.2 X Protocol Version 11, Revision 0 KDE 3.5.9 Netbeans 6.1, 6.5 (attachment was created from screen shot of dev-200810041417) See attachment image for an example (or http://196.25.83.130/netbeans-bug.jpg).
Created attachment 71217 [details] Garbled source when scrolling down large file in Linux
Do you use Sun's JDK or OpenJDK? What's an output from "java -version"? Thanks.
Is this reliably reproducible? Does it always happen with this file? Does it happen with other files too?
Info from the user: Sun JDK java version "1.6.0_07" Java(TM) SE Runtime Environment (build 1.6.0_07-b06) Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
Product Version: NetBeans IDE Dev (Build 200810011401) Java: 1.6.0_07-rev; Java HotSpot(TM) Client VM 10.0-b24 System: Linux version 2.6.24-19-generic running on i386; UTF-8; en_US (nb) I was unable to reproduce the issue with files from TS_65_JavaEditorPerformance (they are much longer than some 2000 lines). Donaldm, can you please send us a sample file that causes the problems?
The problem was not in Netbeans as I could replicate it in a standard Java program opening the same file in a JEditorPane. It appears to be a problem with Java and the Intel i915 driver of the video card in the motherboard I am using. A similar machine I have with a NVidia card and driver works fine and the VESA driver on the original machine also works.
Verified
*** Issue 153875 has been marked as a duplicate of this issue. ***
Any idea how to solve it or a workaround?
hummm, I think I solved the problem just fixing vga driver at my xorg.conf file. The instructions from https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/238629 help me about it. I changed my xorg.conf from Section "Device" Identifier "Configured Video Device" EndSection to Section "Device" Identifier "Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller" Option "AccelMethod" "xaa" Option "RenderAccel" "true" EndSection For now, I can't reproduce the issue.
*** Issue 153857 has been marked as a duplicate of this issue. ***
*** Issue 154649 has been marked as a duplicate of this issue. ***
*** Issue 154680 has been marked as a duplicate of this issue. ***
I updated wiki with the details in http://wiki.netbeans.org/TaT_SolvingEditorGarbledText Regards
Awesome, hmichel... Thank you for this...
*** Issue 156405 has been marked as a duplicate of this issue. ***
*** Issue 156659 has been marked as a duplicate of this issue. ***
*** Issue 157489 has been marked as a duplicate of this issue. ***
With respect to the guidelines of User FAQ Wiki, I have changed the URL (http://wiki.netbeans.org/TaT_SolvingEditorGarbledText ) to make it “FAQSolvingEditorGarbledText”, and that will be updated here as well; http://wiki.netbeans.org/NBCDTipsAndTricks#section-NBCDTipsAndTricks-GeneralTopics
Here's the diff; http://wiki.netbeans.org/Diff.jsp?page=NBCDTipsAndTricks&r1=50&r2=49
*** Issue 157970 has been marked as a duplicate of this issue. ***
Here is the correct link: http://wiki.netbeans.org/FaqSolvingEditorGarbledText
Use XAA is not advisable, and often does not work I use options Exa options MigrationHeuristic and ExaNoComposite Option "AccelMethod" "EXA" Option "MigrationHeuristic" "greedy" Option "ExaNoComposite" "false"
*** Issue 161254 has been marked as a duplicate of this issue. ***
*** Issue 157030 has been marked as a duplicate of this issue. ***
*** Issue 164055 has been marked as a duplicate of this issue. ***
*** Issue 168101 has been marked as a duplicate of this issue. ***
*** Issue 169044 has been marked as a duplicate of this issue. ***
*** Bug 178326 has been marked as a duplicate of this bug. ***
*** Bug 188274 has been marked as a duplicate of this bug. ***