Page 1 of 1

Help needed finding a Planetary Live Stacking bug

Posted: Mon Oct 27, 2025 3:59 pm
by admin
Hi folks,

I'm currently trying to track down the cause of a bug that I am seeing reported in 4.1.13800 that involves a crash while using (or shortly after closing) Planetary Live Stacking. This is probably the most common bug report I am getting at the moment (at least when you discount the ones that basically come down to 'some bit of ASCOM hardware decided to stop working with no warning), so I'm keen to find and fix it. Unfortunately although I have had a number of reports I've not been able to make it happen myself and the reports are not giving me enough info to pin down the exact location of the issue.

If you see a crash report while/after using planetary live stacking that has an error message like

Code: Select all

Disposing of locked buffer of size <some number>, category=Unpooled, lockcount=1
please get in touch, particularly if you can make it happen repeatedly or can describe what you did just before it happened that might have caused it.

The <some number> seems to usually be in the range of 100,000 to 300,000 - corresponding to an image that is smaller than the camera resolution, perhaps due to it being a binned copy of the image or a cut down version due to the use of ROI or the thing in planetary stacking where only a small part of the image initially updates to show new sharpening settings.

Any info regarding this type of crash will help build a picture that will eventually (I hope) point to the cause!

thanks,

Robin

Re: Help needed finding a Planetary Live Stacking bug

Posted: Wed Oct 29, 2025 1:37 pm
by admin
Hi,

OK, I tracked this down - it happens on the 32-bit version of SharpCap only when using MultiPoint stacking. A reference frame used by the multi-point alignment wasn't being cleaned up properly, but the 64-bit version gets away with it while it causes a crash in the 32-bit version. I have a fix which will be in the next update.

cheers,

Robin