Welcome, Guest. Please login or register.
February 21, 2019, 12:49:59 pm

Pages: [1]
  Print  
Author Topic: Possible bug (ANR while playing OXO game in the canteen)  (Read 5219 times)
guybrush
little robot
*
Posts: 2


« on: March 01, 2015, 12:53:48 pm »

I have a problem with Machinarium 1692 on a OnePlus One (Android 4.4.4, SDK ver 14), the issue is always reproducible and is actually blocking me from proceeding in the game.
When playing the "five in a row" game in the canteen, the game freezes after a short while and eventually the OS closes it as ANR. An extract of the stack trace is (I can provide the full logcat if required):


I/DEBUG   (  219): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG   (  219): Build fingerprint: 'oneplus/bacon/A0001:4.4.4/KTU84Q/XNPH05Q:user/release-keys'
I/DEBUG   (  219): Revision: '0'
I/DEBUG   (  219): pid: 16863, tid: 16863, name: .Machinarium.GP  >>> air.net.machinarium.Machinarium.GP <<<
I/DEBUG   (  219): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
I/DEBUG   (  219):     r0 fffffffc  r1 bedc4308  r2 00000010  r3 ffffffff
I/DEBUG   (  219):     r4 71637528  r5 00000000  r6 7163753c  r7 000000fc
I/DEBUG   (  219):     r8 71637570  r9 00000014  sl 4189b408  fp bedc447c
I/DEBUG   (  219):     ip bedc4308  sp bedc42e8  lr 4016c88b  pc 401046e0  cpsr 20030010
I/DEBUG   (  219):     d0  3f80777800000000  d1  000000003f801e57
I/DEBUG   (  219):     d2  0000000000000000  d3  0000000000000000
I/DEBUG   (  219):     d4  00000011418d7938  d5  0000000600000000
I/DEBUG   (  219):     d6  0000000400000003  d7  00000000007a1200
I/DEBUG   (  219):     d8  0000000000000000  d9  0000000000000000
I/DEBUG   (  219):     d10 0000000000000000  d11 0000000000000000
I/DEBUG   (  219):     d12 0000000000000000  d13 0000000000000000
I/DEBUG   (  219):     d14 0000000000000000  d15 0000000000000000
I/DEBUG   (  219):     d16 0000000000004000  d17 0000000000000001
I/DEBUG   (  219):     d18 0000000000000000  d19 0070007300690044
I/DEBUG   (  219):     d20 004500790061006c  d21 0074006e00650076
I/DEBUG   (  219):     d22 006e006e006f0043  d23 0069007400630065
I/DEBUG   (  219):     d24 0000000000000000  d25 4008000000000000
I/DEBUG   (  219):     d26 000000000000000b  d27 0000000000000001
I/DEBUG   (  219):     d28 00000000000000e6  d29 00000000000000e5
I/DEBUG   (  219):     d30 0000000000000001  d31 0000000000004000
I/DEBUG   (  219):     scr 60000010
I/DEBUG   (  219):
I/DEBUG   (  219): backtrace:
I/DEBUG   (  219):     #00  pc 000216e0  /system/lib/libc.so (epoll_wait+12)
I/DEBUG   (  219):     #01  pc 00010887  /system/lib/libutils.so (android::Looper::pollInner(int)+98)
I/DEBUG   (  219):     #02  pc 00010aad  /system/lib/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+92)
I/DEBUG   (  219):     #03  pc 0006ed5d  /system/lib/libandroid_runtime.so (android::NativeMessageQueue::pollOnce(_JNIEnv*, int)+22)
I/DEBUG   (  219):     #04  pc 000204d0  /system/lib/libdvm.so (dvmPlatformInvoke+116)
I/DEBUG   (  219):     #05  pc 0005118f  /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
I/DEBUG   (  219):     #06  pc 00029960  /system/lib/libdvm.so
I/DEBUG   (  219):     #07  pc 00030ea4  /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
I/DEBUG   (  219):     #08  pc 0002e508  /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
I/DEBUG   (  219):     #09  pc 000638a1  /system/lib/libdvm.so (dvmInvokeMethod(Object*, Method const*, ArrayObject*, ArrayObject*, ClassObject*, bool)+392)
I/DEBUG   (  219):     #10  pc 0006ba5f  /system/lib/libdvm.so
I/DEBUG   (  219):     #11  pc 00029960  /system/lib/libdvm.so
I/DEBUG   (  219):     #12  pc 00030ea4  /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
I/DEBUG   (  219):     #13  pc 0002e508  /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
I/DEBUG   (  219):     #14  pc 000635bd  /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+336)
I/DEBUG   (  219):     #15  pc 0004cd6f  /system/lib/libdvm.so
I/DEBUG   (  219):     #16  pc 0005183b  /system/lib/libandroid_runtime.so
I/DEBUG   (  219):     #17  pc 0005255f  /system/lib/libandroid_runtime.so (android::AndroidRuntime::start(char const*, char const*)+354)
I/DEBUG   (  219):     #18  pc 0000105b  /system/bin/app_process
I/DEBUG   (  219):     #19  pc 0000e39b  /system/lib/libc.so (__libc_init+50)
I/DEBUG   (  219):     #20  pc 00000d7c  /system/bin/app_process


It looks scarily similar to the one described here http://stackoverflow.com/q/13482883. I can't tell if the problem lives in the app or in the Adobe AIR runtime. My phone is not rooted so I can't provide more than the logcat I'm afraid, however I submitted a couple of crash reports to Google Play, developers should be able to retrieve them.

Thanks,
Giuseppe
Logged
Alex
Global Moderator
mayor robot
*****
Posts: 665



WWW
« Reply #1 on: March 01, 2015, 09:02:33 pm »

Quote from: guybrush
I have a problem with Machinarium 1692 on a OnePlus One (Android 4.4.4, SDK ver 14)

I apologize for my ignorance, but what is 'Machinarium 1692'?  If it's a version number you should upgrade to the most current supported Android version, which is 2021   Wink

Second, this forum is run by and for fans and there is no direct connection to Amanita Design program support here.  If you wish you can send your query directly to someone that can understand what you're saying via the About tab (up top, between Games & Store).

Lastly, we'd all appreciate if you would kindly post a follow up when your issue gets resolved. 

Good luck.

Logged
guybrush
little robot
*
Posts: 2


« Reply #2 on: March 01, 2015, 11:58:11 pm »

Hi Alex,
1692 is indeed the application build number as reported by the game (intro screen -> star on the bottom right -> "About" -> "Game build 1692 Android"). Google Play reports that I have the latest version installed, 2.0.21 from 20 December 2014, I don't seem to have any way to update to the build 2021 you're mentioning.

I understand what you say about the Forum. I already tried to contact Amanita Design directly using the Contact -> Support form you're mentioning, but 4+ weeks have passed and I got no response. I understand that they could be under pressure, but after all this time they could have leaved a reply.... Anyway the app always sends crash reports to the Google Play store, if they don't ignore them completely I bet they have noticed by now (I've been sending crash reports since January).

I don't really want to just go to the Google Play store and leave a mean comment about the game crashing just to get attention. I was really enjoying the game and I'm trying to be cooperative to solve the issue. But not getting any response from Amanita Design, this forum was my next resort...

Regarding the game build #2021 you're mentioning, are you sure? What is the last version the Google Play store shows you?Me stupid, I just realised than when saying "version 2021" you were talking about the 2.0.21 I already have...

Thanks and regards,
Giuseppe
« Last Edit: March 02, 2015, 09:18:09 am by guybrush » Logged
Pages: [1]
  Print  
 
Jump to: