Yes. It seems that the program crashes earlier when i activate tracking.

Okay, i'll continue to look into this.

Thx man!

I Bought a laptop with windows 7 today and thought that would help.

Crashed in below 20 seconds. this is what the log looks like if it helps you.

.Net Runtime

Application: ARC.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
   at System.Drawing.SafeNativeMethods+Gdip.GdipDrawImageI(System.Runtime.InteropServices.HandleRef, System.Runtime.InteropServices.HandleRef, Int32, Int32)
   at System.Drawing.Graphics.DrawImage(System.Drawing.Image, Int32, Int32)
   at EZ_B.Camera.(System.Object)
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart(System.Object)

Application error

Faulting application name: ARC.exe, version: 2014.11.26.0, time stamp: 0x54760c70
Faulting module name: gdiplus.dll, version: 6.1.7600.16385, time stamp: 0x4a5bd976
Exception code: 0xc0000005
Fault offset: 0x000b31a0
Faulting process id: 0x3d8
Faulting application start time: 0x01d00b562f6b2cfc
Faulting application path: C:\Program Files (x86)\EZ-Robot Inc\ARC.ARC.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7600.16385_none_72fc7cbf861225ca\gdiplus.dll
Report Id: e3261f51-7749-11e4-a43b-001641dcd097

Not too strange it crashed almost instant with the laptop.

The ARC software i Downloaded today 2014-11-26 was set to highest (to the most left) in tracking speed by Default.

Moved the slider a bit to the right and it took atleast 3 minutes until it crashed again.

This is really a strange situation - yesterday I was flying our AR Drone v2 around the office until the batteries died with zero problems. We have many people using the Drone v2 with ARC without issues as well - i'm struggling to understand what can be causing this...

The strack trace mentions a thread - which a cross-threading issue would be my first solution. However, the invoke is called on the object when required and tested successfully yesterday. The access violation tells me the object may be attempted to be referenced twice during threading - but I do not see how that can happen either.

There are no blocks of code missing exception handling throughout the entire video system - .Net is surely behaving different within your environment and I do not know why.

I will create another build for you that removes the threading. It will slow the camera and interface down considerably, but if it works that will identify the issue.

Have you created a project for this example? If so, will you share it with me? Use the ATTACH FILE button in this forum to include the project

DJ, note that he is using a Drone 1, not a 2. Could something have broken when you added support for the 2?

Oh! He's using a v1? How did i not see that - geez! I must be losing my mind, it even says v1 in the subject and it still didn't click

Okay, i have been diving into the v2 code and pulling my hair out. Looks like i need to take a look at the v1 code. I know the v1 works, but haven't spent any time testing toward this issue because I thought it was the v2.