Announcement

Collapse
No announcement yet.

[NI] Game force closes after traveling to the Island area in Android version 1.7.5a

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • [NI] Game force closes after traveling to the Island area in Android version 1.7.5a

    whenever I go to the island it gets closed. sometimes right away and sometimes after a few minutes.

  • #2
    What device do you have. It could be a bug or a memory issue with your device. Before I play I clear the memory and also the cache for the smurfs village app. The memory cache (RAM) on one device is found under smart manager and with my other device I push the home key and the left is the ram and press clear. The cache for smurfs village is found under application manager in settings. I also delete a file called .nomedia which can be found in a sub folder called al within the smurfs village folder found in the android folder in the myfiles app. I find the game functions better.

    Comment


    • #3
      I am experiencing crashes also since 1.7.4 (and also before but less frequently).
      The game crashs every time I visit island, mountain, planet or grove. Just a few seconds after I enter the land (not during travel).
      I am playing on a Samsung tab 2 tablet with Android 4.1.2 :

      Kernel: Linux version 3.0.31-812001 (se.infra@SEP-119) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #1 SMP PREEMPT Wed Mar 20 19:51:29 KST 2013
      Command line: root=/dev/mmcblk0p1 rw rootdelay=2 init=/init vram=15M omapfb.vram=0:8M switch_sel=1 androidboot.emmc_checksum=3 sec_debug.enable=0 sec_debug.enable_user=0 androidboot.debug_level=0x4f4c androidboot.carrier=wifi-only mem=512M@0x80000000 mem=512M@0xa0000000 vmalloc=144m console=sec_log_buf loglevel=0 androidboot.mode=reboot_normal bootmode=0 sec_log=2052K@0x9fdff000 sec_bootfb=8M@0xbef00000 lcd_panel_id=1 androidboot.serialno=c161f8847180460 cordon=9997d40ce9e2ca24e7b7cbbf554b252a

      I try to fresh start the tablet, remove cache, remove files under "al" directory, kill most of background processes, remove wifi, bluetooth and so on... nothing really works.

      I performed a "bugreport" with adb and the diagnosis is a SEGMENTATION FAULT after saving and closing file "miniSaveFriendLoc05.mini". I suspect a memory is used without being allocated when saving map.

      Here are the last lines of report before the crash :
      06-28 15:48:02.773 2634 2649 D CC_Android: Data written | Length: 99544 (97 kbs)
      06-28 15:48:02.773 2634 2649 D CC_Android: **** Closing file "miniSaveFriendLoc03.mini" ****
      06-28 15:48:02.773 2634 2649 D CC_Android: **** Opening file "miniSaveFriendLoc05.mini" to begin writing ... ****
      06-28 15:48:02.781 2634 2649 D CC_Android: Data written | Length: 32 (0 kbs)
      06-28 15:48:02.781 2634 2649 D CC_Android: **** Closing file "miniSaveFriendLoc05.mini" ****
      06-28 15:48:02.781 2634 2649 F libc : Fatal signal 11 (SIGSEGV) at 0x76887000 (code=1), thread 2649 (Thread-317)

      06-28 15:48:02.898 104 104 I DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
      06-28 15:48:02.898 104 104 I DEBUG : Build fingerprint: 'samsung/espresso10wifixx/espresso10wifi:4.1.2/JZO54K/P5110XXDMC2:user/release-keys'
      06-28 15:48:02.898 104 104 I DEBUG : pid: 2634, tid: 2649, name: Thread-317 >>> com.capcom.smurfsandroid <<<
      06-28 15:48:02.898 104 104 I DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 76887000
      06-28 15:48:03.640 104 104 I DEBUG : r0 76886ffc r1 76745de8 r2 00000368 r3 00000146
      06-28 15:48:03.640 104 104 I DEBUG : r4 00000000 r5 00000146 r6 00000000 r7 00000147
      06-28 15:48:03.640 104 104 I DEBUG : r8 00000000 r9 5df52260 sl 00000568 fp 76823008
      06-28 15:48:03.640 104 104 I DEBUG : ip 00000147 sp 5e7321e8 lr 00000000 pc 40061264 cpsr 20000010
      06-28 15:48:03.640 104 104 I DEBUG : d0 00000000ffffffff d1 0000215800000000
      06-28 15:48:03.640 104 104 I DEBUG : d2 00000000ffffffff d3 0000215800000000
      06-28 15:48:03.640 104 104 I DEBUG : d4 000009e00000ffff d5 00000000535b0414
      06-28 15:48:03.640 104 104 I DEBUG : d6 0000000000000000 d7 0000000000000000
      06-28 15:48:03.640 104 104 I DEBUG : d8 4122750000000000 d9 3f0000003f800000
      06-28 15:48:03.640 104 104 I DEBUG : d10 3f8000003f800000 d11 0000000000000000
      06-28 15:48:03.640 104 104 I DEBUG : d12 0000000000000000 d13 0000000000000000
      06-28 15:48:03.640 104 104 I DEBUG : d14 0000000000000000 d15 0000000000000000
      06-28 15:48:03.640 104 104 I DEBUG : d16 0000000000000001 d17 c0f5f90000000000
      06-28 15:48:03.640 104 104 I DEBUG : d18 3ec536fa4149c000 d19 3fe0000000000000
      06-28 15:48:03.640 104 104 I DEBUG : d20 3fe000054dbe9052 d21 bf29ff8d0a5223c0
      06-28 15:48:03.640 104 104 I DEBUG : d22 3f12c03a04dd13f8 d23 3f4347ecbe19cb1d
      06-28 15:48:03.640 104 104 I DEBUG : d24 3f302c9a45084b9a d25 3f6d72eebfda9e35
      06-28 15:48:03.640 104 104 I DEBUG : d26 3f57e0a5d940c01d d27 3f966961c9d0feca
      06-28 15:48:03.640 104 104 I DEBUG : d28 3f822a7ac810437e d29 3faba73040dea49b
      06-28 15:48:03.640 104 104 I DEBUG : d30 0000000000000000 d31 0000000000000000
      06-28 15:48:03.640 104 104 I DEBUG : scr 60000013

      And also a portion of the stack :
      06-28 15:48:03.640 104 104 I DEBUG : backtrace:
      06-28 15:48:03.640 104 104 I DEBUG : #00 pc 0000e264 /system/lib/libc.so
      06-28 15:48:03.640 104 104 I DEBUG :
      06-28 15:48:03.640 104 104 I DEBUG : stack:
      06-28 15:48:03.640 104 104 I DEBUG : 5e7321a8 00000000
      06-28 15:48:03.640 104 104 I DEBUG : 5e7321ac 00000000
      06-28 15:48:03.640 104 104 I DEBUG : 5e7321b0 00000000
      06-28 15:48:03.640 104 104 I DEBUG : 5e7321b4 00000000
      06-28 15:48:03.640 104 104 I DEBUG : 5e7321b8 00000009
      06-28 15:48:03.640 104 104 I DEBUG : 5e7321bc 0000000e
      06-28 15:48:03.640 104 104 I DEBUG : 5e7321c0 00000009
      06-28 15:48:03.640 104 104 I DEBUG : 5e7321c4 00000000
      06-28 15:48:03.648 104 104 I DEBUG : 5e7321c8 00000000
      06-28 15:48:03.648 104 104 I DEBUG : 5e7321cc 00000000
      06-28 15:48:03.648 104 104 I DEBUG : 5e7321d0 00000000
      06-28 15:48:03.648 104 104 I DEBUG : 5e7321d4 00000000
      06-28 15:48:03.648 104 104 I DEBUG : 5e7321d8 00000000
      06-28 15:48:03.648 104 104 I DEBUG : 5e7321dc 00000000
      06-28 15:48:03.648 104 104 I DEBUG : 5e7321e0 df0027ad
      06-28 15:48:03.648 104 104 I DEBUG : 5e7321e4 00000000
      06-28 15:48:03.648 104 104 I DEBUG : #00 5e7321e8 76886e1c
      06-28 15:48:03.648 104 104 I DEBUG : 5e7321ec 5e732360
      06-28 15:48:03.648 104 104 I DEBUG : 5e7321f0 000000c0
      06-28 15:48:03.648 104 104 I DEBUG : 5e7321f4 76722008
      06-28 15:48:03.648 104 104 I DEBUG : 5e7321f8 00000000
      06-28 15:48:03.648 104 104 I DEBUG : 5e7321fc 4008ccab /system/lib/libc.so (memcpy+24)
      06-28 15:48:03.648 104 104 I DEBUG : 5e732200 0006437c
      06-28 15:48:03.648 104 104 I DEBUG : 5e732204 5dd3f16d /data/data/com.capcom.smurfsandroid/lib/libSmurfsAndroid.so (Map::Save(SMap*, char const*, unsigned int)+7220)

      Any clue ?

      Comment


      • debbles smurf
        debbles smurf commented
        Editing a comment
        Your tablet only just passes minimum requirement only barely able to play the game as beeline made changes to minimum requirements so android 4.1 minimum is required to play because of hardware constraints and RAM and other things. My s3 is android 4.3 so I would say the next android kull will include any android device below 4.4 as the device will lack ram and crashing will be a huge issue. Games are a huge memory hog and use evrey bit of spare ram and when that runs out the device will freeze and game will force close.

    • #4
      New !
      After visiting the friends area (which I almost never do because I have no facebook account), it seems to have improved the situation a lot ! Almost no crash and I can visit all the other areas again, dig, plant stuff and so on !
      I suggest everybody to try this...

      Comment

      Working...
      X