Android app crashes when launched in debug mode

Question

When I run in debug mode the app crashes, but when I just run it normally it works. I think the problem happens when the debugger is attached.

Log:

A/art: art/runtime/jdwp/jdwp_event.cc:661] Check failed: Thread::Current() != GetDebugThread() (Thread::Current()=0x7f44a18400, GetDebugThread()=0x7f44a18400) Expected event thread
A/art: art/runtime/runtime.cc:422] Runtime aborting...
A/art: art/runtime/runtime.cc:422] Aborting thread:
A/art: art/runtime/runtime.cc:422] "JDWP" prio=5 tid=4 WaitingForDebuggerSend
A/art: art/runtime/runtime.cc:422]   | group="" sCount=0 dsCount=0 obj=0x12c60280 self=0x7f44a18400
A/art: art/runtime/runtime.cc:422]   | sysTid=24137 nice=0 cgrp=default sched=0/0 handle=0x7f4b904450
A/art: art/runtime/runtime.cc:422]   | state=R schedstat=( 132066712 16401043 106 ) utm=9 stm=2 core=3 HZ=100
A/art: art/runtime/runtime.cc:422]   | stack=0x7f4b80a000-0x7f4b80c000 stackSize=1005KB
A/art: art/runtime/runtime.cc:422]   | held mutexes= "abort lock"
A/art: art/runtime/runtime.cc:422]   native: #00 pc 000000000047e2cc  /system/lib64/libart.so (_ZN3art15DumpNativeStackERNSt3__113basic_ostreamIcNS0_11char_traitsIcEEEEiP12BacktraceMapPKcPNS_9ArtMethodEPv+220)
A/art: art/runtime/runtime.cc:422]   native: #01 pc 000000000047e2c8  /system/lib64/libart.so (_ZN3art15DumpNativeStackERNSt3__113basic_ostreamIcNS0_11char_traitsIcEEEEiP12BacktraceMapPKcPNS_9ArtMethodEPv+216)
A/art: art/runtime/runtime.cc:422]   native: #02 pc 0000000000452434  /system/lib64/libart.so (_ZNK3art6Thread9DumpStackERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEEbP12BacktraceMap+480)
A/art: art/runtime/runtime.cc:422]   native: #03 pc 00000000004403ac  /system/lib64/libart.so (_ZNK3art10AbortState10DumpThreadERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEEPNS_6ThreadE+56)
A/art: art/runtime/runtime.cc:422]   native: #04 pc 0000000000440228  /system/lib64/libart.so (_ZNK3art10AbortState4DumpERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEE+668)
A/art: art/runtime/runtime.cc:422]   native: #05 pc 0000000000433bfc  /system/lib64/libart.so (_ZN3art7Runtime5AbortEPKc+148)
A/art: art/runtime/runtime.cc:422]   native: #06 pc 00000000000e597c  /system/lib64/libart.so (_ZN3art10LogMessageD2Ev+1592)
A/art: art/runtime/runtime.cc:422]   native: #07 pc 00000000002f8458  /system/lib64/libart.so (_ZN3art4JDWP9JdwpState24AcquireJdwpTokenForEventEm+624)
A/art: art/runtime/runtime.cc:422]   native: #08 pc 00000000002f7b1c  /system/lib64/libart.so (_ZN3art4JDWP9JdwpState29SendRequestAndPossiblySuspendEPNS0_9ExpandBufENS0_17JdwpSuspendPolicyEm+248)
A/art: art/runtime/runtime.cc:422]   native: #09 pc 00000000002fcb08  /system/lib64/libart.so (_ZN3art4JDWP9JdwpState16PostClassPrepareEPNS_6mirror5ClassE+1380)
A/art: art/runtime/runtime.cc:422]   native: #10 pc 0000000000124a9c  /system/lib64/libart.so (_ZN3art11ClassLinker11DefineClassEPNS_6ThreadEPKcmNS_6HandleINS_6mirror11ClassLoaderEEERKNS_7DexFileERKNS9_8ClassDefE+804)
A/art: art/runtime/runtime.cc:422]   native: #11 pc 0000000000381d04  /system/lib64/libart.so (_ZN3artL25DexFile_defineClassNativeEP7_JNIEnvP7_jclassP8_jstringP8_jobjectS7_S7_+344)
A/art: art/runtime/runtime.cc:422]   native: #12 pc 00000000001dd40c  /system/framework/arm64/boot-core-libart.oat (???)
A/art: art/runtime/runtime.cc:422]   at dalvik.system.DexFile.defineClassNative(Native method)
A/art: art/runtime/runtime.cc:422]   at dalvik.system.DexFile.defineClass(DexFile.java:296)
A/art: art/runtime/runtime.cc:422]   at dalvik.system.DexFile.loadClassBinaryName(DexFile.java:289)
A/art: art/runtime/runtime.cc:422]   at dalvik.system.DexPathList.findClass(DexPathList.java:418)
A/art: art/runtime/runtime.cc:422]   at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:54)
A/art: art/runtime/runtime.cc:422]   at com.android.tools.fd.runtime.IncrementalClassLoader$DelegateClassLoader.findClass(IncrementalClassLoader.java:90)
A/art: art/runtime/runtime.cc:422]   at com.android.tools.fd.runtime.IncrementalClassLoader.findClass(IncrementalClassLoader.java:62)
A/art: art/runtime/runtime.cc:422]   at java.lang.ClassLoader.loadClass(ClassLoader.java:380)
A/art: art/runtime/runtime.cc:422]   at java.lang.ClassLoader.loadClass(ClassLoader.java:367)
A/art: art/runtime/runtime.cc:422]   at java.lang.ClassLoader.loadClass(ClassLoader.java:367)
A/art: art/runtime/runtime.cc:422]   at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
A/art: art/runtime/runtime.cc:422] Dumping all threads without appropriate locks held: thread list lock mutator lock

I ran into the same problem and it was complete BS. Even restarting the emulator did not help. After removing a bunch of code and then readding it in one block at a time, I arrived back to the original code and the problem was gone. I have a feeling the class object just needed to be rebuilt. A compile went wrong. I'm guessing a project "clean" probably would have fixed it. — Dakusan, Nov 17 '16 at 22:14

score 329 · Accepted Answer · edited Oct 15 '19 at 11:24

329

For me, it occurred when I have a breakpoint in a nested function. In my case, it was within Runnable.run() {}. Not sure if it happens in other nested functions.

Example:

public class TouchEvent {
    public boolean HandleEvent(MotionEvent Event) {
        new Runnable() { @Override public void run() {
            int i=5;
            i++;
        }};
    }
}

If there is a breakpoint on any line inside the run() func, it crashes with the error A/art: art/runtime/jdwp/jdwp_event.cc:661] Check failed: Thread::Current() != GetDebugThread() (Thread::Current()=0x########, GetDebugThread()=0x########) Expected event thread .

This error occurs the first time the class is encountered, NOT when the breakpoint is hit. So it occurred for me when I stepped into a line that had new TouchEvent();, before any of the TouchEvent's code was run (before the constructor).

The solution is to remove the break point (and put it elsewhere).

Edit:

Forgot to mention, it seems to be tied to API25, but has been reported for API26 and API27 too.

Edit:

Another solution is to disabled Instant Run, but please give @toobsco42 credit for that below.

edited Oct 15 '19 at 11:24

Jack T

315
1
6
18

answered Nov 18 '16 at 00:40

Dakusan

6,504
5
32
45

32

This has been reported on code.google.com and I am working on getting it fixed there. https://code.google.com/p/android/issues/detail?id=227513 – Dakusan Nov 18 '16 at 01:00
4

I have sdk 23 and build tools 25.0.1 - same problem. Removing the breakpoints fixes this. – Bonton255 Dec 05 '16 at 20:23
2

You can also remove the breakpoint, press Debug, then once the app is running OK, add it back in to the spot you wanted. Works ok then, just remember to remove it before you restart. – cometfish Jan 24 '17 at 22:26
Same happening to me setting a breakpoint in a `underscore-java` nested `filter` `Predicate` function on Android Studio 2.2.3 – Jaime Agudo Feb 13 '17 at 09:16
3

I switched emulators and problem went away - switched back to original emulator and problem came back. Once the problem appears only way to overcome it (besides clearing all breakpoints - no thanks) is to disable Instant Run. Re-enabling Instant Run on the problem emulator brings the problem back. – Feb 18 '17 at 22:11
11

The issue is a mix of breakpoints in other threads on 7.1.1 with instant run on. So change any of the above 3 and it will stop crashing. – Warpzit Apr 05 '17 at 11:40
I just had to outright disable Instant Run. Even starting the app in debug mode without breakpoints and then adding them later, crashes the app. With Instant Run disabled, it works just fine. My android `buildToolsVersion` is `25.0.3` and gradle-wrapper version is `2.3.3`. – praneetloke Jun 25 '17 at 16:27
I think problem may be created when there are method breakpoints and line breakpoints – Homayoun Behzadian Jul 29 '17 at 15:40
2

I can confirm this on API 26 and buildToolsVersion `26.0.2` as well. – Micer Oct 18 '17 at 08:52
Agreed - I ran into this issue with API 26/buildToolsVersion 26.0.2! – Zach Oct 20 '17 at 03:36
@cometfish That seems very tedious though. – Sreekanth Karumanaghat Apr 18 '18 at 14:53
1

Arggh - wasted so much time on this - thank you for this post ! – GuybrushThreepwood Jun 11 '18 at 13:21

score 187 · Answer 2 · answered Jan 11 '17 at 09:48

187

In my case i had to disable Instant Run. It seems like Instant Run has all sorts of side effects and this can be one of them.

answered Jan 11 '17 at 09:48

Etienne Lawlor

6,817
18
77
89

48

Note, in Android Studio, the is under File -> Settings -> Build, Execution, Deployment -> Instant Run. – shortstuffsushi Feb 07 '17 at 14:37
9

That was an hour of my life I'll never see again – Gary Bak Feb 14 '17 at 20:19
3

Working on multiple machines, with Google constantly reapplying instant run, I'd need it to make me roughly 4216% more efficient when it finally works to remotely come close to getting my lost time back. – Anthony Feb 16 '17 at 13:48
thankss so damn much. should be ticked as answer ;) this ugly feature gives a you a five cent and wastes you a hundred dollars :)) – Amir Ziarati Apr 05 '17 at 10:39
This was *the* answer for me. – slogan621 Jul 16 '17 at 01:27
Thanks worked perfectly.. what's this feature used for anyways? looks like it's just a bloat feature to me. btw this is still affecting Android O and latest android studio RC1 – Desolator Oct 20 '17 at 21:31
Ahhw, Worked, This should be the acceptable answer (API 25) – Naveed Ahmad Nov 02 '17 at 18:00
Perfect! Simple solution – Harshil Pansare Nov 23 '17 at 13:32
This problem seems still to exist. Thank you very much for the workaround. – tangens Aug 31 '18 at 08:45
InstantRun is a shame. I always turn it off these years. It has many side effects. Wasted much time, then realized that InstantRun added bugs. – CoolMind Jun 03 '19 at 09:23
where is "Instant Run" on Android Studio 4.0 ? – Chego Jul 28 '20 at 08:53

hcknl · Answer 3 · 2017-05-05T08:11:47.753

50

Problem is related with Android version 7.x, i removed all the breakpoints in nested functions and it worked, tested with Android version 6.0 too, and it is working without problem.

According to google developers team response, it was fixed on 12/1/2016 and will be applied in next release.

edited May 05 '17 at 08:11

answered Dec 01 '16 at 10:49

hcknl

1,219
10
15

tried all possible, above comment helped! thanks a lot! – Stepan Maksymov Oct 03 '17 at 13:30
It worked, this should be accepted answer. Thanks ! Also, you can remove Instant Run as a another solution – Özer Özcan Dec 28 '17 at 07:29
It would be nice if a link was attached to support this ;) "According to google developers team response, it was fixed on 12/1/2016 and will be applied in next release." – jabu.hlong Feb 28 '18 at 12:39
Probably was an email response, still getting this bug today and had to remove breakpoints – Jim Factor Jun 17 '18 at 22:50
Android 7.1.1 is still the version of Android running on the Pixelbook. I get this all the time developing in Android Studio on the Pixelbook! – Jeff Lockhart Jan 26 '19 at 15:01

score 21 · Answer 4 · answered Sep 29 '17 at 13:04

I removed all the breakpoints and it worked, tested with Emulator Pixel API 25.

To remove all breakpoints:

Go to Debugger option.
Click on red icon which is below to stop debug.
You will see a window there you can remove all breakpoints.

See more in this post: https://stackoverflow.com/a/42478994/5749462

score 16 · Answer 5 · answered Jan 15 '18 at 10:45

16

This is due to some problem with debug points. Remove all the debug points and then it should work.

answered Jan 15 '18 at 10:45

flame3

2,812
1
24
32

4

You can use the shortcut CTRL+SHIFT+F8 to unmark all breakpoints easily. – brunoramonalmeida May 06 '18 at 20:12
This shortcut doesn't work all the time depending your OS and keyboard settings – flame3 May 07 '18 at 06:18

score 8 · Answer 6 · answered Aug 15 '17 at 08:52

8

Its really weird, i disabled Instant Run and the problem solved itself.

answered Aug 15 '17 at 08:52

mbpakalin

177
8
16

Yes, instant run on devices below Android 7.0 may cause this issue quite easily – jujka Jul 02 '18 at 11:22

score 4 · Answer 7 · answered Sep 08 '17 at 11:40

4

My issue was that I had a breakpoint at import statement

answered Sep 08 '17 at 11:40

jujka

1,190
13
18

And ran into this for like third time... Basically, any breakpoint sometimes can cause this, thus the solution may be just to remove all / recent breakpoints – jujka Jul 02 '18 at 11:23

score 4 · Answer 8 · answered Oct 09 '19 at 16:35

My app also crashed only when in debug mode. As for 3.5 version - "Instant Run" was replaced with "Apply Changes", so I could not disable it. My solution was to launch the app normally (with the green arrow), navigate just after the place it used to crash and then to attach the debugger to it:

score 3 · Answer 9 · answered Jun 29 '18 at 15:27

3

In the window 5 : Debug, Use the button "View Breakpoints"

UnSelectAll of them

answered Jun 29 '18 at 15:27

Nicoolasens

2,871
17
22

score 2 · Answer 10 · answered Sep 06 '19 at 05:40

2

Delete All debug points on my application works fine you can use ctrl+shift+f6 to remove all debug points

answered Sep 06 '19 at 05:40

Arun Prajapati

283
2
6

score 1 · Answer 11 · answered Aug 24 '17 at 15:31

Ran into this same issue but my breakpoint was the first line in the nested function so how to move it elsewhere?

I created a temporary private method and made an invocation of that method the first thing in the function and then I set the breakpoint in that method.

When I finished debugging I removed the method and its invocation.

score 1 · Answer 12 · answered Mar 22 '18 at 16:17

1

The simplest solution is trying to find another device or emulator (thanks AVD Manager we have a choice) that will work as charm without workarounds

answered Mar 22 '18 at 16:17

yoAlex5

29,217
8
193
205

score 0 · Answer 13 · answered Jun 12 '17 at 06:55

0

Removing breakpoint from Runable.run() solved the issue for me. I was able to use breakpoints at runtime inside Runable.run(). But not at compile time

answered Jun 12 '17 at 06:55

Ankush

2,405
3
22
45

score 0 · Answer 14 · answered Nov 08 '17 at 16:30

0

it is a long shot but for me, when I have an import statement that isn't being used, and that import has code that runs network calls, it crashed for me but when removing it, the code was able to debug normally.

answered Nov 08 '17 at 16:30

reidisaki

1,525
16
29

score 0 · Answer 15 · answered Nov 14 '17 at 21:01

0

Starting crashing only when starting with debugger. Restarted Android Studio 2.3.2...kept crashing. Runs fine in Run mode. I put in a Log.d() right after onCreate...and it cleared up the problem! Go figure!

answered Nov 14 '17 at 21:01

IrvineCAGuy

211
2
12

score 0 · Answer 16 · answered May 10 '22 at 16:09

for anyone who still have the crashing problem after the above solutions, here's what i have done to fix it on my m1 mac air.

Make sure the select 'wait for debugger' in developer options, and go through other options as well, to make sure they are what you want them to be.

Android app crashes when launched in debug mode

16 Answers16

Linked

Related