Rare memory errors during frame acquisition with Matrox Solios eV-CL

5 次查看（过去 30 天）

Till 2022-5-9

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1715110-rare-memory-errors-during-frame-acquisition-with-matrox-solios-ev-cl

评论： Till 2022-11-19

I have a problem with a Matrox frame grabber (Solios eV-CL). I am using this to capture from a Vieworks VC 4MC180 at fairly high data rates (4K resolution, 100+ fps), which I analyze on the fly; a small ROI is then saved to a video file. I use a videoinput object with a FramesAcquiredFcn to read out the incoming frames (50 at a time, currently).

While in general this works well (sometimes all goes smoothly for more than 100K frames), I occasionally get a memory error of the following sort, disrupting the acquisition:

"Error event occurred at 17:54:18 for video input object: <path to DCF file>

Unable to allocate memory for an incoming image frame due to insufficient free physical memory."

Occurence is unpredictable; sometimes the error occurs shortly after the start of the camera, sometimes after 20 minutes.The machine I am using is nowhere close to its memory limit (used RAM sits solidly at around 7 GB of 32 GB) and I have checked that frames are removed fast enough from the video input object with getdata(). I have the suspicion that it has something to do with the RAM on the frame grabber. I have also tried different acquisition modes (hardware triggered, free-run, etc.), but the error keeps popping up.

Anyone here who has encountered this or a similar error and can shed some light on the issue? Help would be very appreciated.

2 个评论
显示无隐藏无

Sean Sanchez 2022-11-18

I'm seeing some intermittent issues in a similar way. Did you end up resolving this yourself?

Till 2022-11-19

Hi Sean. Sorry, no. This error is very rare, but quite persistent. I still see it in two different applications, so I assume that it does not depend on the specifics of the Matlab implementation.

What kind of issues do you see?

请先登录，再进行评论。

请先登录，再回答此问题。