View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001738 | GeoSetter | User Interface | public | 2017-09-23 15:29 | 2017-09-25 13:17 |
| Reporter | ChrisGorringe | Assigned To | Friedemann | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Platform | Intel x64 | OS | Windows 10 | OS Version | 10.0.15063 |
| Product Version | 3.4.51 beta | ||||
| Target Version | Fixed in Version | ||||
| Summary | 0001738: Exif tool update crash | ||||
| Description | With 3.4.53 beta, I have found a conflict with Netgear Powerline Utility 3.1.0.4. | ||||
| Steps To Reproduce | With this software installed, Geosetter goes into an endless loop whilst trying to update the Exif tool. Using Sysinternals Procmon, it is related to the reading on an XML file using msxml6.dll. Comparing the same process on another machine without the Powerline utility, Geosetter appears to use msxml3.dll. The Powerline utility installs msxml4.dll and when it is uninstalled, Geosetter works perfectly without any further changes having to be made. Reinstalling the Powerline utility then causes Geosetter to stop working again. If left, the process memory allocation keeps increasing and the CPU utilisation endlessly consumes about 15 to 25%. Let me know if you need anything else. | ||||
| Tags | No tags attached. | ||||
|
|
Hi! Thank you very much for finding this out. I will not resolve it. I'm just working a lot on a new version of GeoSetter, where I replace the XML library by an independent library which does not use any external DLLs anymore. But thank you very much, it's good to know! :-) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-09-23 15:29 | ChrisGorringe | New Issue | |
| 2017-09-25 13:02 | Friedemann | Note Added: 0003058 | |
| 2017-09-25 13:17 | Friedemann | Assigned To | => Friedemann |
| 2017-09-25 13:17 | Friedemann | Status | new => assigned |
