Rendering problems for large Java files on macOS

I am using:

- Eclipse 2025-12 (4.38.0)
- Apple MacBook Pro (M2 Max) with Sequoia

Sometimes I am getting performance and rendering problems when working with large Java files. In that case code (in particular at the end of the file is rendered like

Often it helps to close and reopen the Java file, but this kind of performance/rendering problems simply show up from time to time.

I do not have a file which allows to reproduce the problem in an easy way. And I do not want to turn off the annotations etc. Maybe I can change some configuration option in eclipse.ini?

The eclipse.ini file:

```
--launcher.library
../Eclipse/plugins/org.eclipse.equinox.launcher.cocoa.macosx.aarch64_1.2.1400.v20250801-0854
-startup
../Eclipse/plugins/org.eclipse.equinox.launcher_1.7.100.v20251111-0406.jar
-product
org.eclipse.epp.package.jee.product
-showsplash
org.eclipse.epp.package.common
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vm
../Eclipse/plugins/org.eclipse.justj.openjdk.hotspot.jre.full.macosx.aarch64_21.0.9.v20251105-0741/jre/lib/libjli.dylib
-vmargs
-Xmx4096m
-XX:MaxGCPauseMillis=200
-Xss1m
-XX:ReservedCodeCacheSize=512m
-XX:InitialCodeCacheSize=128m
-XX:CompileCommand=quiet
-XX:CompileCommand=exclude org.eclipse.jdt.internal.core.dom.rewrite.ASTRewriteAnalyzer::getExtendedRange
-Dorg.eclipse.ecf.provider.filetransfer.excludeContributors=org.eclipse.ecf.provider.filetransfer.httpclientjava
-Dosgi.requiredJavaVersion=21
-Dosgi.instance.area.default=@user.home/eclipse-workspace
-Dosgi.dataAreaRequiresExplicitInit=true
-Dorg.eclipse.swt.graphics.Resource.reportNonDisposed=true
-Declipse.e4.inject.javax.warning=false
-Dsun.java.command=Eclipse
-Declipse.platform.mergeTrust=true
-XX:+UseG1GC
-XX:+UseStringDeduplication
--add-modules=ALL-SYSTEM
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
-Xdock:icon=../Resources/Eclipse.icns
```

Start by trying to reproduce the rendering and performance issue in Eclipse 2025-12 on macOS with a large Java file, using the supplied eclipse.ini settings as the baseline. Compare the editor after reopening the file and determine a reliable reproduction or diagnostic path; done means the cause is isolated and a verified fix or actionable configuration guidance is available.

Written by the indexing model from the issue text.