Search Issue Tracker

Fixed

Fixed in 4.2.10, 5.1.2, 6.0.0-pre.5

Votes

0

Found in [Package]

4.2.8

5.0.7

5.1.0-pre.10

Issue ID

ARFB-322

Regression

No

[Android] Crash on Android when ARTrackedImageManager Component is added to the AR session origin game object

Package: AR Foundation

-

Reproduction steps:
1. Open the attached project “ARProject”
2. Build and Run the Project on Android
3. Observe the app behaviour

Expected result: The app does not crash
Actual result: The app crashes

Reproducible with: 4.2.8 (2021.3.29f1) 5.0.7, 5.1.0-pre.10(2021.3.29f1, 2022.3.7f1, 2023.1.7f1, 2023.2.0b4)

Reproducible with these devices:
VLNQA00518 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 12
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
VLNQA00278 - Xiaomi Redmi Note 7 (Redmi Note 7), CPU: Snapdragon 660, GPU: Adreno 512, OS: 9.0.0
VLNQA00132 - Xiaomi Mi 5s (MI 5s), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 6.0.1

Reproducible on: macOS(Intel) 13.4.1 Ventura
Not reproducible on: No other environment tested

Note: Crash does not occur in Development Build

First few lines of crash:
{{--------- beginning of crash 08-10 16:34:11.990 11794 11823 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x68 in tid 11823 (GC Finalizer), pid 11794 (com.GradProj) 08-10 16:34:11.991 841 932 I SurfaceFlinger: id=37832 createSurf (6080x6080),2 flag=4, AppWindowToken{8f776e0 token=Token{8192ce3 ActivityRecord{4a5bd12 u0 com.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity t1535}}}#0 08-10 16:34:11.995 3031 3050 D freecess_core: Data received from kernel 08-10 16:34:11.997 1368 3163 D SensorService: Calling activate off 34 08-10 16:34:11.997 798 798 D SensorsBio: Als_common::enable, handle : 1, mode : 0, en : 0 08-10 16:34:11.998 798 798 D SensorsBio: Als_common::sendCommand, send disable command 08-10 16:34:11.999 19370 19370 D ScrollView: initGoToTop 08-10 16:34:11.999 1368 3105 D GamePkgDataHelper: getSosPolicy(). com.google.android.packageinstaller 08-10 16:34:11.999 959 2652 I CameraService: UidPolicy: onUidActive, uid = 10049}}
Log in to vote on this issue

Comments (4)

  1. Trollmo

    Jan 09, 2024 20:10

    I am experiencing the same bug in 5.1.1 on my Oppo Find X2.
    I have read that the quality score of any image in the ReferenceImageLibrary is the cause, and I see a corresponding error message when "Build & Run" is executed.

    Weirdly enough, the pictures in my ReferenceImageLibrary used to work the day before, but after building multiple times with the same component untouched it started crashing.

    I guess there is still no update on the release date?

  2. CiaranWills

    Dec 22, 2023 05:29

    5.1.2 - I can't give any specific dates, but it won't be during the winter break but should be "soon" in the new year.

    As for dynamically adding low quality images, I don't know off-hand. I believe the issue in this case was due to the behavior of the arcoreimg tool during the build so we would need to test.

  3. waldgeist

    Dec 21, 2023 15:05

    When can 5.1.2 be expected to be released? Also, what will happen if images are being added dynamically? Will Android crash again if the quality score hasn't been met?

  4. thomas_key

    Nov 01, 2023 22:33

    We've investigated the issue, and it turns out the "Build" option currently allows a user to bypass the arcoreimg pass/fail check and produces a faulty image library if *any* images fail to meet the quality score of 75. "Build & Run" fails the build correctly and produces an error message.

    We are looking fixing the AR Foundation build process to also fail the build when just "Build" is selected or when a user-made build script is run, as this is the intended behavior.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues