I've been getting some unexpected error messages from Studio6.1 when I run debug-sessions. (Jtag MkIII and UC3xxx processor)
"Atmel Studio was unable to start your debug session.
Please verify device selection, interface settings, target power and connections to the target device."
"Local backend agent has disconnected. Debugging will now be terminated"
The atbacked process consumes about 200Mbytes of virtual-memory every time my debug-session starts and doesn't release it when the debug-session stops.
This means that after a few debug sessions atbacked has used all the available virtual-memory and crashes with the above two error messages.
Fortunately this is just an annoyance, because Windows releases the virtual memory after atbackend has died and the parent atmelstudio process restarts atbacked