gco / xee

Automatically exported from code.google.com/p/xee
72 stars 8 forks source link

Files stay open/locked after Xee stops displaying the image #372

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Go to a directory with more than one image.
2. Open an image with Xee.
3. Skip to the next image using cmd+right. The first image should no longer be 
visible.
4. Move the first image to the trash from the Finder.
5. Attempt to empty the trash. Even though Xee isn't displaying the image in 
question and can't navigate back to it using cmd+[left|right], the file is 
still locked by Xee and the trash can't be emptied.

(or, as an alternative to 4 and 5, just use `lsof` ;)

What version of the product are you using? On what operating system?
This is Xee³ 3.1 (26) on OS X 10.8.4.

Original issue reported on code.google.com by jon.cham...@gmail.com on 28 Aug 2013 at 8:23

GoogleCodeExporter commented 9 years ago
I seem to recall that I investigated that earlier, and came to the conclusion 
that it is an OS X bug. Probably what happens is that OS X creates a sandbox 
exception for the opened file, and there is no way to remove this exception, 
and it will keep the file open. So I can do nothing to fix it.

Original comment by paracel...@gmail.com on 28 Aug 2013 at 8:25