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

BYE 3.1.8 Premium Edition Crashed Tonight


JTWaters

Question

I was taking Dark subs and BYE crashed.  A Win 7 windows popped up for about a second with something about an exception error then everything closed.  BYE was in the middle of taking 1 second Darks and I was stretching a Dark sub to see if there was noise.  The log file is too large to attach.  The last portion of the log file is below.  

 

Equipment

- Win 7 Pro with up to date patches

- Lenovo ThinkPan E440 with 16GBytes of memory

- BYE 3.1.8 Premium Edition 

- 3 Meter USB Repeater Cable

- Canon 6D

 

The battery had a 85% charge and over 125GBytes disk space free.

 

Jim W.

Phoenix, AZ

 

2017-01-11 22:42:03,832 [CameraTakePictureOnMessageRecieved] INFO  - Running (throw): EDSDK.EdsSendCommand(cameraRef, 4, 0)
2017-01-11 22:42:03,910 [CameraTakePictureOnMessageRecieved] INFO  - Success: EDSDK.EdsSendCommand(cameraRef, 4, 0)
2017-01-11 22:42:04,098 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=4)
2017-01-11 22:42:04,098 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=7)
2017-01-11 22:42:04,098 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=0)
2017-01-11 22:42:04,098 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=4)
2017-01-11 22:42:04,098 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=7)
2017-01-11 22:42:04,098 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=1)
2017-01-11 22:42:04,098 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=2)
2017-01-11 22:42:04,098 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=3)
2017-01-11 22:42:04,098 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=4)
2017-01-11 22:42:04,612 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=1)
2017-01-11 22:42:04,612 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=2)
2017-01-11 22:42:04,612 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=3)
2017-01-11 22:42:04,612 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=4)
2017-01-11 22:42:06,126 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=0)
2017-01-11 22:42:06,250 [Main] WARN  - Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
2017-01-11 22:42:06,250 [Main] WARN  -    at BinaryRivers.Common.Extensions.BitmapExtensions.ApplyCurve(Image image, Byte[] levels)
2017-01-11 22:42:06,718 [Main] DEBUG - ObjectEvent_DirItemRequestTransfer: (inRef=317192520)
2017-01-11 22:42:07,436 [OnDirItemRequestTransfer(317192520)] INFO  - Running (log): EDSDK.EdsGetDirectoryItemInfo(inDirItemRef, out dirItemInfo)
2017-01-11 22:42:07,452 [OnDirItemRequestTransfer(317192520)] INFO  - Success: EDSDK.EdsGetDirectoryItemInfo(inDirItemRef, out dirItemInfo)
2017-01-11 22:42:07,452 [OnDirItemRequestTransfer(317192520)] INFO  - Running (log): EDSDK.EdsCreateFileStream(dirItemInfo.szFileName, EDSDK.EdsFileCreateDisposition.CreateAlways, EDSDK.EdsAccess.ReadWrite, out stream)
2017-01-11 22:42:07,467 [OnDirItemRequestTransfer(317192520)] INFO  - Success: EDSDK.EdsCreateFileStream(dirItemInfo.szFileName, EDSDK.EdsFileCreateDisposition.CreateAlways, EDSDK.EdsAccess.ReadWrite, out stream)
2017-01-11 22:42:07,467 [OnDirItemRequestTransfer(317192520)] INFO  - Running (log): EDSDK.EdsDownload(imgRef, dirItemInfo.Size, stream)
2017-01-11 22:42:08,076 [OnDirItemRequestTransfer(317192520)] INFO  - Success: EDSDK.EdsDownload(imgRef, dirItemInfo.Size, stream)
2017-01-11 22:42:08,076 [OnDirItemRequestTransfer(317192520)] INFO  - Running (log): EDSDK.EdsRelease(stream)
2017-01-11 22:42:08,091 [OnDirItemRequestTransfer(317192520)] INFO  - Success: EDSDK.EdsRelease(stream)
2017-01-11 22:42:08,091 [OnDirItemRequestTransfer(317192520)] INFO  - Running (log): EDSDK.EdsDownloadComplete(imgRef)
2017-01-11 22:42:08,216 [OnDirItemRequestTransfer(317192520)] INFO  - Success: EDSDK.EdsDownloadComplete(imgRef)
2017-01-11 22:42:08,216 [OnDirItemRequestTransfer(317192520)] INFO  - Flush Running: (317192392 317192456 317192584 317192520)
2017-01-11 22:42:08,372 [CameraTakePictureOnMessageRecieved] DEBUG - Camera BUSY flushing ObjectsWaitingToBeTransfered...
2017-01-11 22:42:08,590 [Main] WARN  - Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
2017-01-11 22:42:08,590 [Main] WARN  -    at BinaryRivers.Common.Extensions.BitmapExtensions.ApplyCurve(Image image, Byte[] levels)
2017-01-11 22:42:08,809 [OnStateEventHandler] DEBUG - StateEvent_JobStatusChanged Fired! (inParameter=0) (inContext=0)
2017-01-11 22:42:08,809 [OnStateEventHandler] DEBUG - Items transfered!
2017-01-11 22:42:09,386 [CameraTakePictureOnMessageRecieved] INFO  - Flush Running: (317192392 317192456 317192584 317192520)
2017-01-11 22:42:09,480 [ProcessCapture(Normal)] INFO  - Loading image file : C:\Users\JTWaters\Pictures\BackyardTEMP\Download\IMG_0132.CR2
2017-01-11 22:42:09,480 [ProcessCapture(Normal)] INFO  - DCRaw.exe -c -e -T "C:\Users\JTWaters\Pictures\BackyardTEMP\Download\IMG_0132.CR2"
2017-01-11 22:42:09,526 [46] INFO  - Pausing 4 seconds
2017-01-11 22:42:09,558 [ProcessCapture(Normal)] ERROR - Out of memory.
2017-01-11 22:42:09,558 [ProcessCapture(Normal)] ERROR -    at System.Drawing.Bitmap..ctor(Stream stream)
   at BinaryRivers.Common.ImageLoader.DCRaw.Execute(String fullname, String options, Boolean thumbnail)
   at BinaryRivers.Common.ImageLoader.GdRawImageProvider.LoadImage(FileInfo file)
   at BinaryRivers.Common.ImageLoader.GdRawImageProvider.Load(String fullname)
2017-01-11 22:42:09,558 [ProcessCapture(Normal)] ERROR - Unable to load image file error
2017-01-11 22:42:09,558 [ProcessCapture(Normal)] ERROR -    at BinaryRivers.Common.ImageLoader.ImageLoader.Load(String fullpath, Boolean limitsize)
   at OTelescope.BackgroundWorker.Tasks.Image.ProcessCapture.Execute()
Link to comment
Share on other sites

  • Answers 6
  • Created
  • Last Reply

6 answers to this question

Recommended Posts

Hi Jim,

 

I looked at the logs again.

 

2017-01-11 22:42:08,590 [Main] WARN  - Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
2017-01-11 22:42:08,590 [Main] WARN  -    at BinaryRivers.Common.Extensions.BitmapExtensions.ApplyCurve(Image image, Byte[] levels)
2017-01-11 22:42:08,809 [OnStateEventHandler] DEBUG - StateEvent_JobStatusChanged Fired! (inParameter=0) (inContext=0)
2017-01-11 22:42:08,809 [OnStateEventHandler] DEBUG - Items transfered!
2017-01-11 22:42:09,386 [CameraTakePictureOnMessageRecieved] INFO  - Flush Running: (317192392 317192456 317192584 317192520)
2017-01-11 22:42:09,480 [ProcessCapture(Normal)] INFO  - Loading image file : C:\Users\JTWaters\Pictures\BackyardTEMP\Download\IMG_0132.CR2
2017-01-11 22:42:09,480 [ProcessCapture(Normal)] INFO  - DCRaw.exe -c -e -T "C:\Users\JTWaters\Pictures\BackyardTEMP\Download\IMG_0132.CR2"
2017-01-11 22:42:09,526 [46] INFO  - Pausing 4 seconds
2017-01-11 22:42:09,558 [ProcessCapture(Normal)] ERROR - Out of memory.
2017-01-11 22:42:09,558 [ProcessCapture(Normal)] ERROR -    at System.Drawing.Bitmap..ctor(Stream stream)
 
 
The above indicates, and I'm 99.9% sure about this, that .NET was not able to create an in-memory representation of an image for display.  The image file is intact, but .Net has failed to display this image.
 
Now, I'm not sure if this is causing the crash you are reporting, but if this is the root cause this is out of the BYE code base :(
 
Regards,
Link to comment
Share on other sites

BYE is a 32-bit app so Windows caps its memory usage at 2GB, regardless of how much physical memory is available. It seems that you bumped up against that limit.

 

It would be good if you could recreate the error and document the steps that cause it. That may help Guylain figure out if it is possible to free up memory to avoid the issue.

 

Just curious, why are you taking 1 second darks? I would think that dark frames would not be necessary for an images with that short an exposure. Did you have any problem taking the 1 second lights?

Link to comment
Share on other sites

I have never seen this problem before.  This is a laptop that I use for astronomy.  At that time no other apps were running.  The highest that I have seen memory utilization is 2.8 GBytes out of 16 GBytes. This is with TheSky 6 and PHD Guide 2 running at the same time.  

 

I was playing around with a new Rokinon 50mm lens seeing how good the optics were.  Just for the fun of it I was shooting Orion at ISO 1600 with 1 sec subs last night.  I was planning to process the subs with ImagesPlus to determine how much I could resolve Orion with the moon at 98% in a White Zone.  As I mentioned I was stretching a Dark to determine how much noise there was in my Darks.  I pushed the stretch quite a bit.

 

The likelihood of reproducing the problem is slim to none.  Forgot to mention above that their was 4 sec between each sub.

Link to comment
Share on other sites

The first thing I would do would be to reinstall in a new folder and see if it happens again.

 

This seems to be a .net issue where .net is not reserving enough memory to load the image file.  This is a known documented .net issue.

 

Keep us posted.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • 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