Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
  • 0

Out of Memory issues


dlaffoon
 Share

Question

Hello,

Brand new user... first night trying out BYE on Win10 x64 system, 8GB RAM, Core i7 laptop.  I'm connecting to a T3i.  I'm having issues with BYE going unresponsive/freezing up, and a quick forum scan pointed me at log files and I see ample amount of Out Of Memory exceptions occurring.

Two scenarios that cause exceptions:

1) Using frame & focus, live view works for a while (~1min), then everything freezes.

2) Setting up a capture, I can get in maybe 4 frames @ 40s exposure, then all freezes up.

Of note, in #1 above, I watched system RAM utilization while doing a live view, and it just climbed steadily up within a minute until BYE was using ~1.4GB, at which point it froze up.  When doing a capture (#2), I can watch RAM usage slowly creep up while capturing.

Seems like a promising piece of software, but isn't running stable on my system.

Link to comment
Share on other sites

  • Answers 9
  • Created
  • Last Reply

Top Posters For This Question

Popular Days

Top Posters For This Question

Posted Images

9 answers to this question

Recommended Posts

  • 0

You did not say which version of BYE you are using. Please make sure that it is the latest...3.1.16. I do not see the same behavior as you do. BYE 3.1.16 does not become unresponsive for me while running a capture plan. Neither do I see memory usage of my Windows 7 x64 system ramping up while BYE is running in either Frame & Focus or Imaging modes. The left part of the graph was while running a capture plan. The right part was with LiveView active.

 

memuse.png

Any chance that your anti-virus software is causing your issues?

Link to comment
Share on other sites

  • 0

Sorry, should have said it's 3.1.16.

I guess antivirus is a possibility, though I don't know offhand why that would cause this behavior (not allow an app to GC?).

I'll post a screenshot of task manager when I can.

I saw another poster talking about high memory usage in frame and focus on a different post, figured this it possibly another data point.

Link to comment
Share on other sites

  • 0
28 minutes ago, dlaffoon said:

Sorry, should have said it's 3.1.16.

I guess antivirus is a possibility, though I don't know offhand why that would cause this behavior (not allow an app to GC?).

I'll post a screenshot of task manager when I can.

I saw another poster talking about high memory usage in frame and focus on a different post, figured this it possibly another data point.

The issue from that other post you mentioned was fixed several months ago and can not be compared against 3.1.16.

Link to comment
Share on other sites

  • 0

I sent in an example log file to the support email.  I'm really liking the SW, just can't use it for more than 5 minutes at a time right now without having to restart the app.

Any suggestions of extra data I could gather to help figure out what I have going on?

Link to comment
Share on other sites

  • 0
9 minutes ago, dlaffoon said:

I sent in an example log file to the support email.  I'm really liking the SW, just can't use it for more than 5 minutes at a time right now without having to restart the app.

Any suggestions of extra data I could gather to help figure out what I have going on?

I didn't get it.

Link to comment
Share on other sites

  • 0

I've tried another PC (windows 10, desktop i3, 6GB RAM), and it seems happy. RAM usage stays under control, implying the GC is getting to run.  There must be some other interaction on the laptop (original PC) that was conflicting with it.  Maybe AV somehow?  It has McAfee on it.  The desktop's not as portable though :) 

Link to comment
Share on other sites

  • 0

The .NET Garbage Collector does run, when it thinks that it needs to. Even calling GC.Collect() does not force it to run. The call only suggests that it run.

Which SDK is being used? I used Canon215 when I recorded the memory usage graph.

If the unreleased memory is unmanaged, then GC won't see it. In fact, it could be an SDK issue. If this is so, then I would have thought that the issue would be more pervasive.

Just some random thoughts that I hope are useful.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share


×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use