Exception upon opening small matrix after large matrix

Issue #386 resolved
Robert Leach created an issue

USE CASE: WHAT DO YOU WANT TO DO?

Open a small matrix after having opened a large matrix without error.

STEPS TO REPRODUCE AN ISSUE (OR TRIGGER A NEW FEATURE)

  1. Open large_6kx6k.txt
  2. Open small_133x133.cdt

CURRENT BEHAVIOR

The following exception is thrown and the matrix is drawn very small in the top-left corner of the window.

Pixels: 17689
x lies outside raster
 - sun.awt.image.IntegerInterleavedRaster.createWritableChild(IntegerInterleavedRaster.java:461)
 - java.awt.image.BufferedImage.getSubimage(BufferedImage.java:1203)
 - edu.stanford.genetics.treeview.plugin.dendroview.MatrixView.setSubImage(MatrixView.java:467)
 - edu.stanford.genetics.treeview.plugin.dendroview.MatrixView.updateMatrix(MatrixView.java:118)
 - edu.stanford.genetics.treeview.ModelViewProduced.paintComponent(ModelViewProduced.java:125)
 - javax.swing.JComponent.paint(JComponent.java:1053)
 - javax.swing.JComponent.paintChildren(JComponent.java:886)
 - javax.swing.JComponent.paint(JComponent.java:1062)
 - javax.swing.JComponent.paintChildren(JComponent.java:886)
 - javax.swing.JComponent.paint(JComponent.java:1062)
 - javax.swing.JComponent.paintChildren(JComponent.java:886)
 - javax.swing.JComponent.paint(JComponent.java:1062)
 - javax.swing.JComponent.paintChildren(JComponent.java:886)
 - javax.swing.JComponent.paint(JComponent.java:1062)
 - javax.swing.JComponent.paintToOffscreen(JComponent.java:5217)
 - javax.swing.RepaintManager$PaintManager.paintDoubleBuffered(RepaintManager.java:1532)
 - javax.swing.RepaintManager$PaintManager.paint(RepaintManager.java:1455)
 - javax.swing.RepaintManager.paint(RepaintManager.java:1252)
 - javax.swing.JComponent._paintImmediately(JComponent.java:5165)
 - javax.swing.JComponent.paintImmediately(JComponent.java:4976)
 - javax.swing.RepaintManager$3.run(RepaintManager.java:811)
 - javax.swing.RepaintManager$3.run(RepaintManager.java:794)
 - java.security.AccessController.doPrivileged(Native Method)
 - java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:75)
 - javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:794)
 - javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:769)
 - javax.swing.RepaintManager.prePaintDirtyRegions(RepaintManager.java:718)
 - javax.swing.RepaintManager.access$1100(RepaintManager.java:62)
 - javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1680)
 - java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
 - java.awt.EventQueue.dispatchEventImpl(EventQueue.java:744)
 - java.awt.EventQueue.access$400(EventQueue.java:97)
 - java.awt.EventQueue$3.run(EventQueue.java:697)
 - java.awt.EventQueue$3.run(EventQueue.java:691)
 - java.security.AccessController.doPrivileged(Native Method)
 - java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:75)
 - java.awt.EventQueue.dispatchEvent(EventQueue.java:714)
 - java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
 - java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
 - java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
 - java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
 - java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
 - java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
x: -5867 y: -5867 w: 133 h: 133

bad_matrix.png

EXPECTED BEHAVIOR

No error & matrix fills window.

DEVELOPERS ONLY SECTION

SUGGESTED CHANGE (Pseudocode optional)

My suspicions have to do with getMaxIndex, getHoverIndex, or some other similar method returning an index from the previous large file. Note that the negative index returned is the old max index (5999) minus the new max index (132).

FILES AFFECTED (where the changes will be implemented) - developers only

probably MapContainer

LEVEL OF EFFORT - developers only

medium

COMMENTS

I'm experiencing multiple types of these errors since the merges performed last Friday. I checked all 3 of the branches I had merged that day and none of those branches have the error in them.

Comments (3)

  1. Log in to comment