SharpCap freezes after changing ROI

[Imai]

I am experiencing an issue with SharpCap that causes the application to freeze under the following circumstances.
After I have already made a capture, if I change the ROI (Region of Interest), SharpCap becomes completely unresponsive and I am unable to continue using the application.
The only solution is to force-quit the application and restart it. Unfortunately, after restarting SharpCap, all the previously configured parameters are reset, which means I have to set everything up again before I can continue my session.
I have also tested this issue with different cameras, including a Player One Uranus-M and a ZWO ASI174, and the problem occurs with both cameras. This makes me think that the issue may not be related to a specific camera model.

[Menno555]

Hello and welcome

Could you please share a SharpCap logfile after such an event? It makes it easier to see what's going on for Robin.
Here's how to get the logfile: https://docs.sharpcap.co.uk/4.1/16_TroubleShooting.htm

Menno

[admin]

Hi,

yes, as Menno says, a logfile would help a lot here - if the application freezes for about 30s or more then SharpCap tries to record in the log what was going on at the time, and if that info is there then it will point us in the right direction for thinking about how to resolve this.

thanks,

Robin

[Imai]

I've tried it at home now, but it hasn't happened again. I honestly thought it was a bug because it's always happened to me, with different versions of Sharpcap, different PCs, and different cameras. I'll try it again and log it.

[Imai]

reporting.odt

File Log

(50.68 KiB) Downloaded 2 times

It happened again. This is the log after I restarted the app

[admin]

Hi,

unfortunately that doesn't look like the right logfile - what I am seeing in that log is that you opened the camera at full resolution in MONO8, then switched to MONO16, then opened the log. I suspect that is the log file from the run after it crashed

To find the log from the crashed run, you have to go into the folder where the log files are stored and sort the files by date/time order, then find the one with the right timestamp (it will be about the time that you force closed the hung version of SharpCap).

The easiest way to get to the log folder is to run SharCap, choose Help=>Show Log, then press the 'Locate On Disc' button. That will bring up the folder with the log files in. The one that is highlighted in the folder will be the wrong one (the one from the run of SharpCap that you just used to press 'Locate on Disc'), but the older files will be there too.

cheers,

Robin

[Imai]

Log_2026-09-06T11_03_10-18372.log

(262.67 KiB) Downloaded 3 times

Log_2026-09-06T09_18_38-16828.log

(596.49 KiB) Downloaded 1 time

Log_2026-09-06T08_35_57-13344.log

(175.64 KiB) Downloaded 2 times

I’m not entirely sure which log to send, but I can send all the logs from this morning’s session. It’s not actually a crash; the application freezes, and I have to go to the Task Manager on my PC and force it to close because it won't shut down or respond to any input. And I assure you, every time I change the ROI after capturing an image with the camera, the application locks up.

[admin]

Hi,

OK, thanks, this is still very strange...

Two of those logs (the largest and the smallest) seem to run through normally with no errors or problems - ending with a normal shutdown of SharpCap. The other ends with the 'Show Log' window being activated, which would make sense if that was the run of SharpCap that was active when you went looking for the log files. None of them has signs of the user interface becoming unresponsive...

I wonder if rather than becoming unresponsive, the UI is somehow stuck being unable to update what is on the screen? Can you try going to the SharpCap settings (the 'General' tab) and untick the option for 'Use graphics card acceleration...' - then restart SharpCap and see if that helps at all.

If that doesn't help, the next thing would be to try to catch another log file, but this time if you could also try to record the time at which the problem with the app becoming non-responsive happens then it would help me ensure we are in the right log and that I am looking at the right part.

thanks,

Robin