Author Topic: Bug when trying clone stamp  (Read 902 times)

Offline stouchtidis

  • Newcomer
  • Posts: 6
Bug when trying clone stamp
« on: 2018 January 06 18:10:21 »
I'm using PI under Windows 10 (latest updates applied). I open a saved Mask (nothing else open) then select Clone Stamp process. I ctrl-click on a location, and drag. Then I try to move the cursor and get a PCL Win32 System Exception *which I cannot escape*-- I click OK and it keeps coming back. Please see attached snip of the error (At address 00007FFCA32E1E99 with exception code C0000005 : Access violation: invalid memory read operation at address FFFFFFFFFFFFFFE8).

I may be mis-clicking or something (I've not used Clone Stamp before in PI) but regardless, the endless pop-up loop which stops me from continuing shouldn't be happening.




Offline pfile

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 4729
Re: Bug when trying clone stamp
« Reply #1 on: 2018 January 06 18:55:25 »
we see stuff like this on dell systems sometimes... is it a dell machine?

rob

Offline stouchtidis

  • Newcomer
  • Posts: 6
Re: Bug when trying clone stamp
« Reply #2 on: 2018 January 06 21:48:49 »
Yes it is. An XPS something or other, I can find the exact model if it helps.

I finally figured out how to avoid the problem, but it was pretty annoying while it was going on!

Anyway, take care of more urgent business, just keep in mind for future.

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: Bug when trying clone stamp
« Reply #3 on: 2018 January 10 03:00:50 »
Hi,

I cannot reproduce this problem with PixInsight 1.8.5 on any of our working and testing machines, including Windows 10, 8.1 and 7 SP1. One of these machines is a Dell laptop with a 4K screen and Windows 10, where PixInsight works nicely with zero problems.

Try resetting all application settings. Launch the application with the Ctrl key pressed and answer yes to the subsequent confirmation dialog. This may fix these issues in case they are being caused by a wrong configuration. I have seen this happen in a few cases with users that had older versions installed.
Juan Conejero
PixInsight Development Team
http://pixinsight.com/