I am writing to report a persistent issue with the Sashimi Plot functionality in IGV 2.17.4.
The Problem Description: When I right-click a transcript and select "Sashimi Plot," the new visualization window opens but fails to render the coverage tracks and junction arcs. Only the gene/transcript annotation track at the bottom is visible; the data visualization area above it remains completely blank/white. This occurs for all transcripts I attempt to plot.
Environment and Configuration:
IGV Version: 2.17.4 (Portable/ZIP distribution)
OS: Windows 10
Java Version: 17.0.10 (System default, as bundled JDK was not found/used)
System RAM: 32 GB
Data Files: BAM and GTF files are successfully loaded and displayed in the main IGV window. File paths have been restricted to use only ASCII characters (no Chinese or special characters) to rule out encoding issues.
Exhaustive Troubleshooting Steps Taken (Failure to Resolve):
To rule out memory, compatibility, and rendering issues, I have attempted the following steps without success:
Increased Memory Allocation: Set the -Xmx parameter in igv.bat to 8g.
Windows DPI Scaling Fix: Applied the "Override high DPI scaling behavior" (set to "System") compatibility setting to the system's core java.exe file, addressing common Java Swing rendering issues on high-resolution Windows screens.
Forced Software Rendering: Explicitly edited the igv.bat file to add the Java 2D parameter -Dsun.java2d.d3d=false to the startup command, disabling hardware acceleration to resolve potential graphics driver conflicts.
Log Analysis: The console output confirms no fatal Java Exceptions (such as OOM or Null Pointer) are thrown when the blank Sashimi window is launched, indicating a rendering logic failure rather than a thread crash.
Console Log Snippet: (A full log file is attached/provided below)
Given that all standard workarounds have failed, I believe this may be a bug within the Sashimi Plot's drawing component when running on this specific Windows/Java 17 environment.
Could you please confirm if this is a known rendering bug in version 2.17.4, or suggest any alternative older versions that are less prone to such graphics issues?
Thank you for your assistance.
Best regards

