Search Issue Tracker
By Design
Votes
3
Found in
2018.2.0a1
2018.2.0f2
Issue ID
1061714
Regression
Yes
[Android] AndroidJavaObject().Call<string> crashes with Fatal signal 11(SIGSEGV)
Steps to reproduce:
1. Open user attached project
2. Build & Run on Android device
3. Observe that a crash occurs when the app is started
Expected result: Fatal signal 11(SIGSEGV) crash should not occur when starting application
Reproduced in: 2018.3.0a5, 2018.2.0f2, 2018.2.0a1
Not reproduced in: 2018.1.9f1, 2017.4.7f1, 2017.2.3p1
Regression since: 2018.2.0a1
Tested devices:
Samsung Galaxy S9 (SM-G960F), 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
Sony Xperia Z2 (D6503), 6.0.1, CPU: Snapdragon 801 MSM8974PRO-AB, GPU: Adreno (TM) 330
-
yurabereza
Jul 19, 2018 15:57
What does it mean - by design? Is it not possible in 2018.2 to call functions from android which returns null string references?
-
yurabereza
Jul 19, 2018 06:47
Have the same issue. Look's like Unity is trying to call strlen on NULL string (If Java method returns null instead of some string)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
Yury-Habets
Aug 02, 2018
The issue here was with the user's project, hence the resolution "by design". Please submit another bug report with your project attached if you face any JNI issues.
Thanks!