v3.1.5 Out of memory error

[Andrew Cool]

Hi Guylain,

 

I was running two instances of v3.1.5 (copied the main.exe file to another name), and after some unknown time,

both instances apparently ran out of memory. See attached screen dump.

 

The two instances of BEOS were the only programs running under WIn 7 Pro 64 bit with 16GB of RAM on board.

 

Any log files that I can send ?

 

Andrew Cool

 

 

 

[admin]

You can't do that; it messes up the configuration files.

 

If you want to start a second instance you need to use the camera2.exe.

 

Regards,

[astroman133]

Follow the instructions here:

 

http://www.otelescope.com/index.php?/topic/219-how-to-setup-backyardeos-to-use-two-2-cameras/#entry7247

[Andrew Cool]

You can't do that; it messes up the configuration files.

 

If you want to start a second instance you need to use the camera2.exe.

 

Regards,

Hi Guylain,

 

On  reading the instructions for the Master/Slave environment for use with Cameras1/2/3/4, it didn't really seem to suit my

needs, where I have the two cameras each taking different length exposures. I recalled that with a previous recent version, your instructions were

to copy and rename the .exe file, which seemed to work AOK.

 

Anyway, it was working AOK last night too, until I retired to the car to get some sleep, came out again before dawn to find the Out of Memory errors.

The logs do complain a lot about writing to protected memory locations, which may be symptomatic of the config fiels getting muddled?

 

I didn't have time to actually try this out at home before deploying to the bush, as my laptop died during the week, and I'd spent the morning before leaving

frantically re-loading software onto a reformatted drive.

 

Andrew

 

PS : Question. Will the Master/Slave setup handle one camera imaging every 45 seconds and the second camera imaging every 120 seconds?

[admin]

Don't worry about the master/slave mumbo jumbo, you don't need to use it... but if you want to run 2 instances of BYE you need to use camera2.exe regardless of if you want them synchronized or not.

 

Copying the .exe to another name has never been supported because the exe will not have a configuration file and BYE depends on it.  For this reason it will not work and I can not recall ever saying that it would knowing this huge constraint.

 

Out of memory does not mean you are running out of memory.  Wait, what?  When an image is loaded a memory space is allocated and the image is loaded into that location.  If the memory allocated for the image being loaded is not sufficient Windows will throw an out of memory error.

 

Send me the log file and I can confirm this (or not).

 

Please make sure your .Net 4.0 is up do date as the out of memory error is a .net error.

 

Keep us posted,

[s3igell]

There have been threads with instructions on how to get Multiple Camera Instances running which have detailed Copying the Camera1.exe file to new instances (with the same done for the Config file):

 

How to setup BYEOS to use 2 Cameras

How can I use 2 Canon 40Ds on 2 Scopes simply

 

Perhaps this is where the idea was planted that Andrew Cool has pursued...

The trick may be in the details of HOW he has done so...

 

I know that I've followed the Instructions in the above Threads (I contributed to them) to successfully run 2-Camera/2-Mount and 2-Camera/1-Mount Imaging Configurations - in the pre-v3.1.5 days without direct Sync support.  And had decent Success (caveats posted in those threads).

 

But, I'd never encountered any Out-of-Memory Errors on a modest 8GB Laptop.

[Andrew Cool]

Don't worry about the master/slave mumbo jumbo, you don't need to use it... but if you want to run 2 instances if BYE you need to use camera2.exe regardless of if you want them synchronized or not.

 

Copying the .exe to another name has never been supported because the exe will not have a configuration file and BYE depends on it.  Forthis reason it will not work and I can not recall ever saying that it would knowing this huge constraint.

 

Out of memory does not mean you are running out of memory.  Wait, what?  When an image is loaded a memory space is allocated and the image is loaded into that location.  If the memory allocated for the image being loaded is not sufficient Windows will throw an out of memory error.

 

Send me the log file and I can confirm this (or not).

 

Please make sure your .Net 4.0 is up do date as the out of memory error is a .net error.

 

Keep us posted,

 

Hi Guylain,

 

Log files attached. They are all from the same evening.

 

The laptop had a clean install of Windows and every available update was installed, running dotnet 4.5.2

 

The reason for many logs is that I was previewing the raws with the new 64 bit version of Irfanview, but it

displayed the raws as 160x120 pixel images, but JPEGS at fullsize! That really threw me for a while until I tracked the

culprit down to Irfanview and not BEOS.

 

Andrew

[Andrew Cool]

Hi Guylain,

 

Log files attached. They are all from the same evening.

 

The laptop had a clean install of Windows and every available update was installed, running dotnet 4.5.2

 

The reason for many logs is that I was previewing the raws with the new 64 bit version of Irfanview, but it

displayed the raws as 160x120 pixel images, but JPEGS at fullsize! That really threw me for a while until I tracked the

culprit down to Irfanview and not BEOS.

 

Andrew

Hello Guylain,

 

All is AOK. Last night I used the camera.one and camera.two executables, and both cameras ran for 4 hours without a hitch.

Clearly I did something stupid the first night. But then, if you asked my wife, she'd tell you that's my normal state of existence.. ;-)

 

All I need now from BEOS is the ability to determine the start time of Astronomical Darkness for a given lat/long location, and to then start

an imaging plan automatically that runs until Astronomical Darkness ends before Dawn.

 

Thanks for a great porgram,

 

Andrew

[s3igell]

All I need now from BEOS is the ability to determine the start time of Astronomical Darkness for a given lat/long location, and to then start

an imaging plan automatically that runs until Astronomical Darkness ends before Dawn.

One of the best resources: Sunrise Sunset Calendar

 

One would want it to factor in whether the Target is East or West of the Meridian (darker sooner to the East), time of Moodnrise/Moonset, and any local Light Domes and Zodiacal /Gegenschein Light and...

One would also want support for an All-Sky Camera (with Cloud Detection - of course) and some sort of Anemometer Interface as well as a Real-time Clock NTP (with full Daylight Savings detail) and... (never ends)

 

Guylain has stated on a few occasions that his intention is to keep BYE/BYN Simple and Focused as an Astro Imaging App.

If you are looking for Lots more (and willing to be confused at every turn), then you might wish to explore Sequence Generator Pro or MaximDL.

[Jim]

Ref. keeping BYE simple - Guy did some while ago say he would start work on a "cloud away" feature but this would be an expensive premium edition ;^))

 

I'm still waiting.

 

Jim