Hi Rae,

Sorry, even though floating keyboard was mentioned, it didn't occur to me
to use the windows on screen keyboard to send the emoji. I will try this
again when I get home to my windows machine. I will probably be able to get
back to you around 5:30 CT on whether or not I can reproduce this crash.

George

On Tue, Aug 16, 2016 at 11:38 AM, Wree, Rae <[email protected]> wrote:

> Hi George,
>
>
>
> This crash is occurring when we use the floating keyboard in Windows 10 to
> send an emoji to an Android client. It crashes on an HTC One M8 running
> Android 5.0.1. It does not crash if we use emojis from the Android
> keyboard, so β€œπŸ˜Šβ€ (from Windows) crashes but β€œβ˜ΊοΈβ€ (from Android)
> doesn’t.  For me, the chat app crashed when I pasted the Windows smile into
> chat on an Android 6.0.1 device, which can handle them, then sent it via
> chat to the HTC One M8.
>
>
>
> Rae
>
>
>
> *From:* George Tang [mailto:[email protected]]
> *Sent:* Monday, August 15, 2016 9:11 PM
> *To:* Kevin Kane <[email protected]>
> *Cc:* Blayney, Jeff <[email protected]>; allseen-core@lists.
> allseenalliance.org; Poole, Gary <[email protected]>; Cazier, Robb P
> (CEPS SW Development) <[email protected]>; Wree, Rae <[email protected]>;
> Truong, Binh <[email protected]>
> *Subject:* Re: Java Binding Crash
>
>
>
> Hi,
>
>
>
> I was able to build the master branch on win10 and run the chat.exe file.
> I was able to send emojis to the win10 machine by sending emojis from my
> android device and copying and pasting the output in the windows chat
> sample and resending them. The chat app did not crash on the Android
> device, and the android device is running the 5.1 Android OS. I have
> attached screenshots.
>
>
>
> Looking at the logs, it seems that the crash happens in the Android layer.
> I looked up the error, and the following link may give you an idea of a
> workaround (note that their runtime is dalvik instead of art):
> http://stackoverflow.com/questions/16786739/how-to-use-
> unicode-in-android-resource .
>
>
>
> Your Android runtime is ART, so you must at least be running on an Android
> 4.4 OS. I can't offer much information on what each OS can and can't do. I
> think it may be safe to say that emoji's work on 5.1 and above, given my
> testing. But if you are running 5.1 or above, I will probably investigate
> more.
>
>
>
> George
>
>
>
>
>
> On Mon, Aug 15, 2016 at 7:00 PM, George Tang <[email protected]> wrote:
>
> Hi,
>
>
>
> I was able to send a birthday cake emoji with the chat sample application
> on Android. The chat sample application is using bus signal to send chat
> messages.
>
>
>
> I've attached the screenshot of the emoji. The device that sent the emoji
> is an Android 5.1. The device that received the emoji is an Android 6.0.
> The chat sample was from the alljoyn 15.04 android release sdk on the
> allseenalliance.org site.
>
>
>
> I will try testing the emojis with the master branch on a windows 10
> computer. I'm not sure how I would send an emoji through the command line
> chat sample though.
>
>
>
> George
>
>
>
> On Mon, Aug 15, 2016 at 6:32 PM, George Tang <[email protected]> wrote:
>
> Hi,
>
>
>
> I will take a look.
>
>
>
> George
>
>
>
> On Mon, Aug 15, 2016 at 5:36 PM, Kevin Kane <[email protected]> wrote:
>
> George has been doing some work on the Java binding lately, and may have
> some insight here.
>
> If JIRA can't handle the stack trace pasted into the ticket itself, you
> should be able to create the ticket and then attach the stack trace as a
> text file afterwards. Definitely create a ticket that at least describes
> the problem, though, so we're sure to track the issue.
>
>
> -----Original Message-----
> From: [email protected] [mailto:
> [email protected]] On Behalf Of Blayney, Jeff
> Sent: Monday, August 15, 2016 3:23 PM
> To: [email protected]
> Cc: Poole, Gary <[email protected]>; Cazier, Robb P (CEPS SW
> Development) <[email protected]>; Wree, Rae <[email protected]>; Truong,
> Binh <[email protected]>
> Subject: [Allseen-core] Java Binding Crash
>
> Hello,
>
> I tried to log a bug but Jira chokes on the pasted stack trace. I figured
> I’d send out a quick email to see if we can get some short-term workaround
> help.
>
> Question: Who maintains the Java bindings?
>
> We are seeing an issue on the receiving side of a signal. If there is an
> emoji character in a MsgArg with signature of β€œs” or β€œss”, it will crash.
> Here is a stack trace:
>
> This is high priority for us, and I figure there is a possibility its
> simple fix. Is anyone available to take a quick look?
>
> Thanks for any assistance!
>
> This happens when we use the Windows 10 floating keyboard to send an emoji
> to Android. Crashes before it gets to our code.
>
> 08-08 13:57:09.046 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65] JNI DETECTED ERROR IN APPLICATION: input is
> not valid Modified UTF-8: illegal start byte 0xf0
> 08-08 13:57:09.046 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]     string: '{"device_id":"54615243-E554-
> 458B-9CD2-17434804BEF9","new_clips":[{"attributes":{"data":"πŸŽ‚
> ","type":"text"},"clip_id":"43c53c91-9772-4b77-ad96-
> 768f4586cb4e","device_id":"54615243-E554-458B-9CD2-
> 17434804BEF9","device_name":"DESKTOP-3V9PJH6","time_stamp":
> 1470686228.2892799,"type":"text","visibility":"all"}]}'
> 08-08 13:57:09.046 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]     in call to NewStringUTF
> 08-08 13:57:09.046 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]     from java.lang.String
> org.alljoyn.bus.MsgArg.getString(long)
> 08-08 13:57:09.046 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65] "Thread-990" prio=5 tid=30 Runnable
> 08-08 13:57:09.046 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   | group="main" sCount=0 dsCount=0
> obj=0x1308ec40 self=0xb83ad698
> 08-08 13:57:09.046 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   | sysTid=20003 nice=0 cgrp=apps sched=0/0
> handle=0xb831d3c0
> 08-08 13:57:09.046 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   | state=R schedstat=( 0 0 0 ) utm=0 stm=0
> core=0 HZ=100
> 08-08 13:57:09.046 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   | stack=0xa06fe000-0xa0700000 stackSize=252KB
> 08-08 13:57:09.046 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   | held mutexes= "mutator lock"(shared held)
> 08-08 13:57:09.046 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   native: #00 pc 00004828
> /system/lib/libbacktrace_libc++.so (UnwindCurrent::Unwind(unsigned int,
> ucontext*)+23)
> 08-08 13:57:09.046 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   native: #01 pc 00002ec5
> /system/lib/libbacktrace_libc++.so (Backtrace::Unwind(unsigned int,
> ucontext*)+8)
> 08-08 13:57:09.046 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   native: #02 pc 0024441d
> /system/lib/libart.so (art::DumpNativeStack(std::__1::basic_ostream<char,
> std::__1::char_traits<char> >&, int, char const*,
> art::mirror::ArtMethod*)+68)
> 08-08 13:57:09.046 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   native: #03 pc 002277eb
> /system/lib/libart.so (art::Thread::DumpStack(std::__1::basic_ostream<char,
> std::__1::char_traits<char> >&) const+394)
> 08-08 13:57:09.046 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   native: #04 pc 000af2b3
> /system/lib/libart.so (art::JniAbort(char const*, char const*)+582)
> 08-08 13:57:09.056 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   native: #05 pc 000af9f9
> /system/lib/libart.so (art::JniAbortF(char const*, char const*, ...)+60)
> 08-08 13:57:09.056 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   native: #06 pc 000b1e8b
> /system/lib/libart.so (art::ScopedCheck::Check(bool, char const*, ...)
> (.constprop.135)+882)
> 08-08 13:57:09.056 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   native: #07 pc 000ba931
> /system/lib/libart.so (art::CheckJNI::NewStringUTF(_JNIEnv*, char
> const*)+36)
> 08-08 13:57:09.056 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   native: #08 pc 00090ccc
> /data/app/com.hp.orbit-1/lib/arm/liballjoyn_java.so
> (_JNIEnv::NewStringUTF(char const*)+12)
> 08-08 13:57:09.056 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   native: #09 pc 00093150
> /data/app/com.hp.orbit-1/lib/arm/liballjoyn_java.so
> (Java_org_alljoyn_bus_MsgArg_getString+88)
> 08-08 13:57:09.056 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   native: #10 pc 00269f89
> /data/dalvik-cache/arm/data@[email protected][email protected]@
> classes.dex<mailto:/data/dalvik-cache/arm/data@app@com.
> [email protected]@classes.dex> (Java_org_alljoyn_bus_MsgArg_
> getString__J+88)
> 08-08 13:57:09.056 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   at org.alljoyn.bus.MsgArg.getString(Native
> method)
> 08-08 13:57:09.056 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   at org.alljoyn.bus.MsgArg.
> unmarshal(MsgArg.java:319)
> 08-08 13:57:09.056 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]   at org.alljoyn.bus.MsgArg.
> unmarshal(MsgArg.java:392)
> 08-08 13:57:09.056 19858-20003/com.hp.orbit A/art:
> art/runtime/check_jni.cc:65]
> 08-08 13:57:09.296 19858-20003/com.hp.orbit A/art:
> art/runtime/thread.cc:812] pthread_getschedparam failed for DumpState: No
> such process
> 08-08 13:57:09.296 19858-20003/com.hp.orbit A/art:
> art/runtime/runtime.cc:284] Runtime aborting --- recursively, so no
> thread-specific detail!
> 08-08 13:57:09.296 19858-20003/com.hp.orbit A/art:
> art/runtime/runtime.cc:284] ______________________________
> _________________
> Allseen-core mailing list
> [email protected]
>
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2flists.
> allseenalliance.org%2fmailman%2flistinfo%2fallseen-core&
> data=01%7c01%7ckkane%40microsoft.com%7c8e8fd26c7c7a457ebed508d3c55ac561%
> 7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=3g4g0XA%
> 2bIDDjdCBwgRyDkR07dIVGw1qyJ9EG60UJW%2bM%3d
>
>
>
>
>
>
>
_______________________________________________
Allseen-core mailing list
[email protected]
https://lists.allseenalliance.org/mailman/listinfo/allseen-core

Reply via email to