Had GSAK lock up today whilst publishing logs.
I selected a photo to add to a log.
Publish log Edit -> Images button.
Add - Select image.
Entered caption, hit Ok.
GSAK returned to the Images list, showed a thumbnail and stopped responding.
Task manager showed GSAK.exe using 25% cpu after about three minutes. (Quad core i5 - so using an entire core)
No response from the program and had to kill the process from TM.
I was *extremely* grateful that GSAK had saved all my publish log records up to that one as I'd spent almost an hour logging in great detail today's finds.
The photo came from an Oregon 650. I believe something may have been wrong with it, as although Explorer showed it perfectly, I also use the Windows 7 Image resizer power toy. I used that on it, and for the first time I've ever seen it fail, it errored with "too much meta data changed".
So suspect this additional library may not cope gracefully with bad jpgs.
I selected a photo to add to a log.
Publish log Edit -> Images button.
Add - Select image.
Entered caption, hit Ok.
GSAK returned to the Images list, showed a thumbnail and stopped responding.
Task manager showed GSAK.exe using 25% cpu after about three minutes. (Quad core i5 - so using an entire core)
No response from the program and had to kill the process from TM.
I was *extremely* grateful that GSAK had saved all my publish log records up to that one as I'd spent almost an hour logging in great detail today's finds.
The photo came from an Oregon 650. I believe something may have been wrong with it, as although Explorer showed it perfectly, I also use the Windows 7 Image resizer power toy. I used that on it, and for the first time I've ever seen it fail, it errored with "too much meta data changed".
So suspect this additional library may not cope gracefully with bad jpgs.