Error on breakpoint in M36
See original GitHub issueRepro: Install M36 RC build. Create sample project. Set breakpoint on counter++ line. Tap counter button in app. Error generated when breakpoint hit.
Access is allowed from event dispatch thread only.
com.intellij.openapi.diagnostic.RuntimeExceptionWithAttachments: EventQueue.isDispatchThread()=false Toolkit.getEventQueue()=com.intellij.ide.IdeEventQueue@727485ce
Current thread: Thread[ApplicationImpl pooled thread 3,4,Idea Thread Group] 1444411203
SystemEventQueueThread: Thread[AWT-EventQueue-0,6,Idea Thread Group] 907030465
at com.intellij.openapi.application.impl.ApplicationImpl.assertIsDispatchThread(ApplicationImpl.java:1133)
at com.intellij.openapi.application.impl.ApplicationImpl.assertIsDispatchThread(ApplicationImpl.java:1122)
at com.intellij.ui.AppIcon.assertIsDispatchThread(AppIcon.java:672)
at com.intellij.ui.AppIcon.access$300(AppIcon.java:51)
at com.intellij.ui.AppIcon$MacAppIcon.requestFocus(AppIcon.java:208)
at com.intellij.ide.impl.ProjectUtil.focusProjectWindow(ProjectUtil.java:333)
at io.flutter.server.vmService.DartVmServiceDebugProcess$1.sessionPaused(DartVmServiceDebugProcess.java:102)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.util.EventDispatcher.dispatchVoidMethod(EventDispatcher.java:133)
at com.intellij.util.EventDispatcher.access$100(EventDispatcher.java:25)
at com.intellij.util.EventDispatcher$3.invoke(EventDispatcher.java:96)
at com.sun.proxy.$Proxy153.sessionPaused(Unknown Source)
at com.intellij.xdebugger.impl.XDebugSessionImpl.positionReachedInternal(XDebugSessionImpl.java:882)
at com.intellij.xdebugger.impl.XDebugSessionImpl.breakpointReached(XDebugSessionImpl.java:776)
at com.intellij.xdebugger.impl.XDebugSessionImpl.breakpointReached(XDebugSessionImpl.java:738)
at io.flutter.server.vmService.DartVmServiceListener.onIsolatePaused(DartVmServiceListener.java:183)
at io.flutter.server.vmService.DartVmServiceListener.lambda$received$0(DartVmServiceListener.java:82)
at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:314)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Troubleshoot Breakpoints in the Visual Studio Debugger
If a breakpoint is disabled or couldn't be set, it's displayed as a hollow circle. Look here information on problems that can occur...
Read more >Setting Error Breakpoints - MuleSoft Documentation
To set the error parameter for the application, click the errors button. in the Mule Breakpoints view. This parameter causes any Event Processor...
Read more >I cannot set breakpoint - Visual Studio Feedback
In Visual Studio 2019 16.7.1 I cannot set a breakpoint. Error: Microsoft Visual Studio. Visual Studio has encountered an unexpected error.
Read more >Error settings breakpoints but only on some lines while ...
The breakpoint and single-step behavior you're describing is usually caused by attempting to debug your project in a "Release" build ...
Read more >Error Breakpoints :: Editing and Debugging M-Files ... - MatLab
To set error breakpoints, select Debug -> Stop if Errors/Warnings. In the resulting Stop if Errors/Warnings for All Files dialog box, specify error...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think it is because the active window is the emulator (unless using a phone) and we want the debugger to pop to top.
On Thu, May 30, 2019 at 1:25 PM Devon Carew notifications@github.com wrote:
👍 That should do it.