Clone Stamp died, please help!

[stouchtidis]

I have been using Pixinsight (including CloneStamp) successfully for several months.

Yesterday, CloneStamp (after having worked well for a while) started generating a Windows error message right after I do Ctrl-Click to select a point. The error message is attached.

Incidentally this error message recurs several times before it will clear for a few seconds and allow me to close the Clone Stamp module.

NOTE: This bug survived uninstall and reinstall of Pixinsight, so I'm at a loss as to what's going on.

It is NOT image specific, but it appears to happen when I'm using CloneStamp at 1:1 magnification and larger, and does not happen when I'm zoomed out more.  (However CloneStamp *was* working before this issue started using 1:1 and even more zoomed-in views).

My system has more than 200GB of available disk space on the SSD, and is an i7 system with 32GB RAM, so it should not be a resources issue. Windows 10 with all the updates.

[pfile]

is it by chance a dell machine?

rob

[stouchtidis]

Yes it is.

[pfile]

maybe try this: https://pixinsight.com/forum/index.php?topic=9190.0

there's some conflict between dell's utilities and PI - i think the dell utils also use Qt and the dell utils install a very old version of some Qt DLL that interferes with PI.

rob

[stouchtidis]

For the record, deleting Global Preferences and starting with the Pixinsight-Reset Settings shortcut (suggested by a Cloudy Nights user) fixed the issue.

No idea why the settings would have survived Uninstall and Reinstall.

[pfile]

the problem might come back... the dell issues seem random. if it does, be prepared to go hunting for and uninstalling the dell utils.

rob

[stouchtidis]

I don't use the Dell Utils at all, so I don't quite see how they would be responsible. Uninstalling them wouldn't uninstall the DLL in question would it?

I find it hard to believe that resetting settings fixed the problem if the problem was not *in* the settings.

[pfile]

of course if the uninstaller is proper, then yes, it will uninstall the offending DLL as well.

i guess none of us really know what resetting the settings actually does. if it in any way causes windows to reload a bunch of DLLs then you have a race condition; if whatever DLL that exports the function that's segfaulting gets loaded 2nd, then i suppose you're in for a world of hurt.

rob