Thank you ).. And Yes, that is what this update is for.

Perhaps watching the video will help.

Software hang and memory leak?

I was gingerly messing with some functions on my robot (camera motion specifically), when I noticed noise starting to appear in the processed feed. I know that means my battery is about to drop out. So I unplugged the battery from the board.

Now the software has locked up, and according to the Task Manager, its slowly consuming more and more RAM.

The app doesn't say "Not Responding", but it IS frozen.

That wouldn't be so bad had I not messed with a bunch of changes I would have liked to save : (

Any thoughts on how to "unfreeze" the app?

P.S.

Latest build and Firmware (5/29/14).

I learned the hard way to periodically save my projects.... Lost an hours work once when my computer locked up.... Sorry I don't have anything more constructive to say....

@cyberdude can you post your project so I can examine to see what could have caused that?

Also, by "memory leak"... how much more RAM was being used and how much was it climbing? I will take a look and see...

I run extensive tests before releases, which is why ARC is so amazingly efficient even on slow low memory computers.

Will post project this evening. As for Mem. It was gaining quickly initially, about 4K every couple seconds. After half an hour, 2K every 15 sec. Or so.

App unresponsive the whole time. It didn't indicate "unresponsive", just frozen.

What I did to unfreeze (though it killed the app) was to kill Bluetooth. (Pulled it out), that forced the app to die.

The memory increase is too small of increments to be a memory leak due to the camera feed - because the memory for the camera is much larger and would increase in megabytes not kilobytes, which is good news. The reason for the increase is most likely due to the debug log filling with internal error messages. I believe the debug log window was not able to become visible due to the GUI freezing from the error. So the log was filling with messages, but you were unable to see that because the GUI was frozen.

I will review your project and hopefully recreate the situation and fix it, like I do

My V3s would occasionally freeze up ARC if they disconnected (i.e. if my robot run away during testing). No "Not Responding" messages just totally unresponsive to anything.

I found that if I went to task manager and ended the application it would prompt ARC to ask if I wanted to exit and if I wanted to save, these were both operational which meant saving of work could be made. It didn't fix ARC being unresponsive though but after a save and restarting ARC all was fine.

Interesting, thanks Rich! I'll need to see projects - preferable minimum number of controls that causes it to happen. The less controls the better for identifying what can cause it.