NOTICE! This is a static HTML version of a legacy ImageJ Trac ticket.

The ImageJ project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Ticket #905 (closed defect: wontfix)

Opened 2011-12-05T15:34:15-06:00

Last modified 2014-08-19T11:19:30-05:00

Overlays can disappear

Reported by: bdezonia Owned by: bdezonia
Priority: major Milestone: imagej2-b9-rois
Component: Legacy Compatibility Version:
Severity: serious Keywords:
Cc: Blocked By:
Blocking: #1011


Open boats. Draw two overlays quickly right after loading. Wait a while and overlays go away.

I think Harmonization is happening after the overlays are drawn (since maybe it took a while for threads to terminate). And it is not seeing the overlays drawn by the user.

Change History

comment:1 Changed 2012-01-19T12:08:45-06:00 by bdezonia

  • Milestone changed from imagej-2.0-beta1 to imagej-2.0-beta2

comment:2 Changed 2012-01-20T12:51:35-06:00 by bdezonia

We may need to set a mode in IJ2 that keeps someone from adding data to an image that is currently the image of interest to an IJ1 plugin. Once IJ1 returns and synchronization is complete the lock would be lifted. Note that this could make deadlock possible if IJ1 plugin does not terminate.

On a related note right now it takes a surprisingly long time to wait for threads to terminate before synchoronization even runs. See why that is the case too.

comment:3 Changed 2012-02-15T15:47:02-06:00 by bdezonia

In a3ba7159826fbb9a60585340613d3cceb0782ef2 thread waiting time decreased. It is now harder for this bug to happen but it is still possible.

comment:4 Changed 2012-02-26T22:30:02-06:00 by curtis

  • Blocking 1011 added

comment:5 Changed 2012-05-14T11:01:46-05:00 by bdezonia

  • Milestone changed from imagej-2.0.0-beta3 to imagej-2.0.0-beta4

comment:6 Changed 2012-09-10T09:13:35-05:00 by bdezonia

  • Milestone changed from imagej-2.0.0-beta4 to imagej-2.0.0-beta6

comment:7 Changed 2014-08-19T11:19:30-05:00 by curtis

  • Status changed from new to closed
  • Resolution set to wontfix

We are no longer supporting use of ImageJ 1.x commands or data synchronization from modern ImageJ2 UIs. So this bug is moot.