PixInsight Forum (historical)

PixInsight => Bug Reports => Topic started by: Adrien on 2019 November 22 03:46:06

Title: BLINK. Releasing Memory causes Access Violation.
Post by: Adrien on 2019 November 22 03:46:06
Hello.
I am using PI version  1.8.8.1
I have not seen this problem before. When moving images to Rejected Folder, or closing Blink, I get a Memory Access Violation. Please attached screen shot.
I am running WIN 10 with latest 1909 update, although this problem was apparent before the latest Win update. I have run memory diagnostics, and it shows OK, and re-booted the PC a few times.
Appreciate any advice to solve this problem.
Regards
Adrien Richardson
Title: Re: BLINK. Releasing Memory causes Access Violation.
Post by: Juan Conejero on 2019 November 26 02:13:21
Hi Adrien,

Please check if this continues happening on version 1.8.8-2. Anyway, we cannot reproduce this problem on any platform, neither with 1.8.8-1 nor with 1.8.8-2. Blink works perfectly in all of our tests. If this continues happening, can you please upload a data set where you can reproduce this problem?
Title: Re: BLINK. Releasing Memory causes Access Violation.
Post by: Adrien on 2019 November 26 07:26:52
Hello Juan

I know you are very busy, so I appreciate your time.
I uploaded 17 or so frames to Dropbox. These cause the problem.

https://www.dropbox.com/sh/e0rd3c0a2nrkc8q/AACdQBYzjtGNJvgHxiochE-Ea?dl=0

Best Regards
Adrien

Title: Re: BLINK. Releasing Memory causes Access Violation.
Post by: Adrien on 2019 November 26 07:30:32
I forgot to add this is with 1.8.8-2
Title: Re: BLINK. Releasing Memory causes Access Violation.
Post by: Juan Conejero on 2019 November 26 10:05:03
Hi Adrien,

Thank you for uploading this data. As expected, I cannot reproduce this problem with your images. Blink continues working without flaws on all of our Windows 10 machines (and of course on the rest of supported platforms) with the images you have uploaded.

Can you describe your machine:

- CPU model
- Amount of RAM
- Graphics card(s)

Also, can you try after updating your graphics drivers as I describe in this post (https://pixinsight.com/forum/index.php?topic=12995.msg85786#new)?