View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001292||GeoSetter||User Interface||public||2016-01-03 18:31||2017-05-16 22:50|
|Product Version||3.4.51 beta|
|Target Version||Fixed in Version|
|Summary||0001292: File handle resource leak on save, which eventually causes unpredictable behaviour and even data loss and crashes|
|Description||It looks like there is a resource leak during save operations. Eventually the number of open handles gets to be too large and saves start failing, or incorrect data is saved, or the application even crashes.|
|Steps To Reproduce||1) Open a folder with a couple of thousand files. I had CR2+JPG, but I've seen this in folders with only JPGs.|
2) Select all of the files. Hit Ctrl+E to edit. Change the timezone of the first file and copy this to all of them. Close the edit dialog
3) Open Windows' Task Manager. On the Processes tab (Windows 7) add the "Handles" column. Note the number of open handles of the GeoSetter.exe process
4) Hit Ctrl+S to save.
5) Watch the handles count. When it finishes saving note the new number. If you continue working in GeoSetter this number will keep going up.
|Additional Information||I think I hit problems faster (too many handles) with folders with CR2 with XMP and JPG sidecars, but this is just an impression. Does GeoSetter update both the XMP and JPG when saving the data?|
Running this against a fileset on my Mac via SMB has also resulted in OS X running out of file handles and causes random application crashes on the Mac. I've seen it bring down VMware Fusion, but note that the problem also occurs when using a separate PC running Windows natively.
I'm attaching a dump of the GeoSetter.exe's open handles
|Tags||No tags attached.|