ST keeps crashing

[Melty]

Hi Ivo,

Well I just reverted back to the old non-GPU version and when I attempted to mask out the irregular gaps around the edge of my mosaic (it's not rectangular) in the Wipe module, the app still crashed.

Here's the log up to that point:

-----------------------------------------------------------
StarTools 1.9.536alpha
Sat Jan 14 11:28:29 2023
-----------------------------------------------------------
File loaded [B:\MOSAIC\2nd TRY\New folder\Combined_All.tif].
Image size is 16319 x 14338
---
Type of Data: Non-linear sRGB source
--- RoI Optimized Develop
Parameter [Ignore Fine Detail <] set to [6.0 px]
Parameter [Outside RoI Influence] set to [15 %]
Parameter [RoI X1] set to [0 px]
Parameter [RoI Y1] set to [0 px]
Parameter [RoI X2] set to [16319 px (-0)]
Parameter [RoI Y2] set to [14338 px (-0)]
Parameter [Detector Gamma] set to [1.00]
Parameter [Shadow Linearity] set to [50 %]
--- Crop
Parameter [X1] set to [1800 px]
Parameter [Y1] set to [14250 px]
Parameter [X2] set to [13701 px (-2618)]
Parameter [Y2] set to [1 px (-14337)]
Image size is 11901 x 14251
--- Bin
Parameter [Mode] set to [Integer Mean]
Parameter [Scale] set to [Scale 50.00% / +2.00 bits / +1.00x SNR Improvement]
Image size is 5950 x 7125

Regards

Taking it from there, and assuming a Windows OS, can you confirm you have sufficient virtual memory allocated? (at least 2xphysical, so 96GB in your case)

Are there any other memory-hungry applications running at the same time?

Are you running StarTools from a drive that is formatted as NTFS? (FAT32 may not allow StarTools to create large enough Tracking files).

Can you confirm the drive you are running StarTools from has sufficient free space available?

What is the nature of the crash - does StarTools just disappear, or is there some sort of dialog?

Thank you,

Yes, Windows 10.

ST is installed on Windows 1TB NVME NTFS SSD, currently with 163GB free space.

No memory hungry apps running (task manager shows ST using no more than about 25gb of RAM before crashing).

ST will simply disappear, with zero prior warning.

I've just rerun the previous scenario, but changed the original System Managed page file (7600MB) to a custom one based off your recommendations (8000-96000MB). Rebooted the PC, relaunched ST and still it crashes without warning.

Thanks

[admin]

At least one bug confirmed (it's a timing bug in Wipe that happens when it has to wait long for the system to release and re-allocate memory).
Working on a fix for the next 1.9 alpha - I will release it today or tomorrow.
Thank you for reporting and for your patience!

EDIT: After fixing the bug, I still got an OOM condition at the original 170 megapixel size on my 32GB test system, but that's to be expected. The 42.3MP (after binning, as you did in your workflow) dataset worked OK.

[admin]

Can you please try 1.9.539 alpha (now up for download) and let me know if the issue persists? Thank you!

[Melty]

Hi Ivo,

I've managed to complete a full editing run in (non-GPU) ST without issue. It appears your fix worked.

Only fly in the ointment seems to be some garbled text when I open the Optidev module after Wipe.

Region Of interest (&language-roi;) is active.

I'm sure this will be addresed in the next release.

Thank You!

[admin]

Only fly in the ointment seems to be some garbled text when I open the Optidev module after Wipe.

Ointment now fly-free.

[Melty]