App actually does run fine on ART outside of a debug session but consistently fails when started from a Fire Debug session (not tried with VS). I’m aware ART is developer only etc etc but rumours are that it will be default on 5.0.
LogCat: W/ActivityThread(20454): Application the_app_that_keeps_on_giving is waiting for the debugger on port 8100…#00 pc 00022fd8 /system/lib/libc.so (strlen+83)#01 pc 000811bd /system/lib/libart.so (art::Dbg::GetSourceFile(unsigned long long, std::string&)+104)#02 pc 000e737b /system/lib/libart.so#03 pc 000e9adf /system/lib/libart.so (art::JDWP::JdwpState::ProcessRequest(art::JDWP::Request&, art::JDWP::ExpandBuf*)+386)#04 pc 000eb3f9 /system/lib/libart.so (art::JDWP::JdwpState::HandlePacket()+36)#05 pc 001d6fa7 /system/lib/libart.so (art::JDWP::JdwpAdbState::ProcessIncoming()+1138)#06 pc 000eb5ef /system/lib/libart.so (art::JDWP::JdwpState::Run()+378)#07 pc 000ec86b /system/lib/libart.so#08 pc 0000d170 /system/lib/libc.so (__thread_entry+72)#09 pc 0000d308 /system/lib/libc.so (pthread_create+240)#00 47bf99f0 00000000#01 47bf99f0 00000000#02 47bf9a38 416f3e00 /system/lib/libart.so
Thanks, logged as bugs://68725: Fire: Cannot debug on ART runtime
ck
July 18, 2014, 11:39am
3
Can you try with the next beta? It works now for me (art on Nexus7)
bugs://68725 got closed as fixed for release Fire
Sadly not fixed. Fire crashes on launch of the app. There’s no crash dump apart from:
19/07/2014 16:36:32.291 com.apple.launchd.peruser.501[161]: (com.remobjects.oxygene.Fire.219328[48459]) Exited with code: 255
…in the Console. The target app that Fire installed on the device runs outside of Fire.
This is on Android 4.4.4 on a Nexus 4 using the ART runtime.
OK, It’s working on Dalvik (from Fire). I’m going to switch back to ART to double check.
I will say however that this release seems more crash prone than before. If the debugger goes down it usually takes Fire with it.
I can confirm it’s definitely still not working on ART. I see a load of ClassNotFound Exception warnings (pretty usual) and then Fire crashes.
I don’t know if the cause is the same but VS also fails to run the app under ART. Here’s the log from VS:
An exception of type: java.lang.ClassNotFoundException occurred#00 pc 00021f90 /system/lib/libc.so (tgkill+12)#01 pc 00012fe1 /system/lib/libc.so (pthread_kill+48)#02 pc 000131f5 /system/lib/libc.so (raise+10)#03 pc 00011f2b /system/lib/libc.so#04 pc 00021844 /system/lib/libc.so (abort+4)#05 pc 00017621 /system/lib/libstlport.so (std::__stl_throw_overflow_error(char const*)+6)#06 pc 0019b09b /system/lib/libart.so#07 pc 0019b813 /system/lib/libart.so (art::StackVisitor::WalkStack(bool)+314)#08 pc 00077c61 /system/lib/libart.so (art::Dbg::GetThreadFrameCount(unsigned long long, unsigned int&)+808)#09 pc 000e6853 /system/lib/libart.so#10 pc 000e9adf /system/lib/libart.so (art::JDWP::JdwpState::ProcessRequest(art::JDWP::Request&, art::JDWP::ExpandBuf*)+386)#11 pc 000eb3f9 /system/lib/libart.so (art::JDWP::JdwpState::HandlePacket()+36)#12 pc 001d6fa7 /system/lib/libart.so (art::JDWP::JdwpAdbState::ProcessIncoming()+1138)#13 pc 000eb5ef /system/lib/libart.so (art::JDWP::JdwpState::Run()+378)#14 pc 000ec86b /system/lib/libart.so#15 pc 0000d170 /system/lib/libc.so (__thread_entry+72)#16 pc 0000d308 /system/lib/libc.so (pthread_create+240)#00 47c0e808 00000006#01 47c0e820 00000006#02 47c0e830 47c0e83c [stack:12457]
ck
July 28, 2014, 6:16am
9
Yes it is. What (project) did you use to reproduce this?
@ck Errrr…well it wasn’t working on the last but one beta. I don’t know about this week’s. The project was the one I sent you at the weekend for the internal error. I think that drop of the project builds and runs for Android so maybe you could try it with that? As I say I’ve not tried running on ART for over a week.
ck
July 28, 2014, 9:33am
11
ck
July 28, 2014, 2:30pm
12
I’m uploading a new build (preview for fridays build); can you try it with this one? (should be up in ~5 minutes after this post)
@ck I’ll have a look asap tomorrow.
Still crashing for me with the original trace:
An exception of type: java.lang.ClassNotFoundException occurred#00 pc 00022fd8 /system/lib/libc.so (strlen+83)#01 pc 000811bd /system/lib/libart.so (art::Dbg::GetSourceFile(unsigned long long, std::string&)+104)#02 pc 000e737b /system/lib/libart.so#03 pc 000e9adf /system/lib/libart.so (art::JDWP::JdwpState::ProcessRequest(art::JDWP::Request&, art::JDWP::ExpandBuf*)+386)#04 pc 000eb3f9 /system/lib/libart.so (art::JDWP::JdwpState::HandlePacket()+36)#05 pc 001d6fa7 /system/lib/libart.so (art::JDWP::JdwpAdbState::ProcessIncoming()+1138)#06 pc 000eb5ef /system/lib/libart.so (art::JDWP::JdwpState::Run()+378)#07 pc 000ec86b /system/lib/libart.so#08 pc 0000d170 /system/lib/libc.so (__thread_entry+72)#09 pc 0000d308 /system/lib/libc.so (pthread_create+240)#00 47bd19f0 00000000#01 47bd19f0 00000000#02 47bd1a38 416dbe00 /system/lib/libart.so
ck
July 29, 2014, 6:02am
15
Thats with the build I uploaded for you on personal downloads?
Yes, that build. I also did a clean build and deleted the previous build of the app off of the device. It crashes pretty much within a second or two of launch.
ck
July 29, 2014, 7:38am
17
hrmm. It’s not actually the app that fails, what’s happening is that android’s ART debug server implementation isn’t thread safe. The protocol states that it should be, but it isn’t. I locked down all places I could think of that do two things at once, and I couldn’t reproduce the issue after that anymore so it’s strange that it still happens for you.
Android components that don’t do what they say they do? Never!
Which Android OS are you testing with? I’m on 4.4.4 on a Nexus 4. I could try a Nexus 7 later if that’s what you test on.
steveflack
July 29, 2014, 10:49am
19
@ck If there’s anything more I can do to help let me know.
ck
July 29, 2014, 4:28pm
20
Can you try again (uploaded a new build with teh same version nr)? I think I got it. You’ll need to manually compile Sugar and use a project ref to it.
