PHD crashes after running some hours with error "not enough memory"

[moritz8712]

My PHD2 2.6.10 runs nicely and then after several hours all of a sudden crashes with the message in the debug file:

"invoke imagearray: [8007000e]  Not enough storage is available to complete this operation". Any clue what could be wrong?

Moritz

[bw_msgboard]

This is more likely to be a problem with whatever computer system you're running.  Thousands of us are running PHD2 all night long without encountering these kinds of errors.  What OS platform are you running?  We would need to see your debug log file to know anything about it.

 

Bruce

---

From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of moritz8712
Sent: Tuesday, October 12, 2021 11:46 AM
To: Open PHD Guiding
Subject: [open-phd-guiding] PHD crashes after running some hours with error "not enough memory"

My PHD2 2.6.10 runs nicely and then after several hours all of a sudden crashes with the message in the debug file:

"invoke imagearray: [8007000e]  Not enough storage is available to complete this operation". Any clue what could be wrong?

Moritz

--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/4ff4ba00-f589-4ab2-97d4-02d517a5597bn%40googlegroups.com.

[moritz8712]

I have a i7-3630 Windows 10 laptop with 16 GB of RAM. So the RAM really should be more than enough. And I never had RAM issues with other programs. But PHD crashed now the second time in a row during a night session.

[Patrick Chevalley]

The error message "Not enough storage is available to complete this operation" is given by the ASCOM camera driver when PHD2 ask for the image data.

There can be multiple reason for that:

- a bug in the camera driver can make it to try to allocate a terabyte buffer.

- a bug in the camera driver can prevent it to release the memory from the previous images, slowly exhausting the computer memory.

- a bug in any other running application that make it to exhaust the computer memory.

In any case this is something specific to your installation because it work fine for anyone else even with much smaller computer configuration.

To prevent the first two case be sure you install the latest available driver from the camera manufacturer.

Then use the Windows task manager to look at the running application memory usage to find the one with increasing memory usage over the time.

In the case you find this is PHD2, repeat the same but with a profile using the ASCOM camera simulator instead of your real camera.

Patrick

[moritz8712]

Thank you! I will try that in my next run. By the way, it came to my mind that I had activated in the PHD global settings that guiding images are stored. And during that session 1.6 GB of pictures were stored. Could this also be correlated to the error? As I understood you, this error comes from the camera driver and not from PHD. Anyway, I now deactivated the storage.

Moritz

[Patrick Chevalley]

This is probably not related to the stored images.

But as Bruce indicate, we really need a full debug log of a session that show the issue before we can do anything on the PHD2 side.

For me the problem is most probably external to PHD2, this is why I ask you try that even before to see the log.

Patrick

[moritz8712]

Hello together

I made a new try tonight. I updated my QHY 5 II camera with the latest driver and, to be on the safe side, I also deselected the storage of images. But PHD crashed again after five hours. I attached the log file. 

If it is the driver of the camera, then it surprises me, since it is a guiding camera which is on the market for many years. I should not be one of the first to run into such a bug.

Regards,

Moritz

[Patrick Chevalley]

This the guide log, it normally not contain useful information for this case.

But this is strange, this log say it use a Sony camera for guiding?  are you sure of the configuration and not using the same camera for guiding and imaging.

Otherwise we need the debug log, if possible with the QHY camera, and to avoid to send a big file by email use the "Upload log" feature from the PHD2 help menu.

See this page for more information: https://openphdguiding.org/getting-help/

Patrick

[Brian Valente]

>>> If it is the driver of the camera, then it surprises me, since it is a guiding camera which is on the market for many years. I should not be one of the first to run into such a bug.

it's not just the camera

I guide with my QHY 5II all the time without issues. Sounds like it's something in your configuration/setup

You might try re-downloading the latest QHY drivers, they have really changed recently and QHY seems to have cleaned it up quite a bit. 

Brian

--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/8a70fe9f-9bdd-4565-88f2-2654e9e8b351n%40googlegroups.com.

--

Brian 

Brian Valente

portfolio brianvalentephotography.com 

[moritz8712]

Ok, now I got it with the debug log file. Here is the link to my upload: https://openphdguiding.org/logs/dl/PHD2_logs_cfvm.zip

The situation with the sony is the following.: Last night I first tried to use a sony camera with a normal camera tele lens. But the focus was bad and the guiding did not work well. So I stopped it again and changed to my normal guide scope with the QHY 5II which did smooth guiding from the start. So it was the same setup as the night before, but with the updated driver. And again it crashed after a few hours of normal working.

Yes, I downloaded the latest driver from QHY yesterday and installed it. But still the same problem. 

Thank you!

Moritz

[bw_msgboard]

It looks like there are a number of unusual things here compared to what we normally see - the ASCOM version of the camera driver, a mount driver that is unusual, and an imaging app that is using an obsolete interface for controlling PHD2.  I suggest that you pare things down to the essentials and do some testing - like this:

 

1.  Use the native QHY driver, not the ASCOM driver.

2.  Connect only the guide camera in PHD2 - no mount connection at all

3.  Don't use any imaging application.

 

Once you have only the native QHY camera driver connected, you can start running tests in the daytime.  Just start PHD2 looping and let it run for at least 6 hours.  If that works, you can then try going back to the QHY ASCOM driver and if the problem returns you can work with QHY to resolve it.  In any case, once you have a solid solution with the guide camera, reconnect the mount but still without the imaging application.  This will need to be tested at night unless you want to use a pulse-guiding test application that I can send you.  If the problem returns, you'll know it's coming from the mount ASCOM driver.  Once you get all that sorted out, you can restore use of the imaging application or find another one that is using the modern server interface in PHD2.

 

Hope you can isolate the problem quickly,

Bruce

---

From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of moritz8712

Sent: Thursday, October 14, 2021 7:04 AM
To: Open PHD Guiding
Subject: Re: [open-phd-guiding] PHD crashes after running some hours with error "not enough memory"

--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/8a70fe9f-9bdd-4565-88f2-2654e9e8b351n%40googlegroups.com.