title: Android Studio Flutter debugging FileSystemException
body: <p>I am developing a <strong>Flutter</strong> application in <strong>Android Studio</strong>. When I place a breakpoint somewhere in the code it gets hit and execution stops, but after half a second the application exits with the following error:</p>
  
  <pre><code>Unhandled exception:
  FileSystemException: Cannot open file, path = 'build\app.dill.track.dill.incremental.dill' (OS Error: The requested operation cannot be performed on a file with a user-mapped section open.
  , errno = 1224)
  #0      _File.open.&lt;anonymous closure&gt; (dart:io/file_impl.dart:364:9)
  #1      _RootZone.runUnary (dart:async/zone.dart:1379:54)
  #2      _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
  #3      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
  #4      Future._propagateToListeners (dart:async/future_impl.dart:668:32)
  #5      Future._completeWithValue (dart:async/future_impl.dart:483:5)
  #6      Future._asyncComplete.&lt;anonymous closure&gt; (dart:async/future_impl.dart:513:7)
  #7      _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
  #8      _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
  #9      _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:115:13)
  #10     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:5)
  Unhandled exception:
  SocketException: Write failed (OS Error: The pipe is being closed.
  , errno = 232), port = 0
  #0      _rootHandleUncaughtError.&lt;anonymous closure&gt; (dart:async/zone.dart:1112:29)
  #1      _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
  #2      _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
  #3      _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:115:13)
  #4      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:5)
  </code></pre>
  
  <p>If I run application without debugging it works normally. Has anyone had similar error and solved it successfully?</p>