ARCore crash (0000000001968e44) #1374
Assignees
Labels
Comments
|
|
Hi @devbridie unfortunately, I received a call from a client today with the same issue I have. The Stacktrace from the GooglePlayConsole looks like this |
|
If it is important on my device is for Google Play-Service for AR the version 1.30.220390193 installed. |
|
@devbridie hey, I think it's a combination of the Depth-API and SceneForm. The Crash can be reproduced with this sample App https://github.com/SceneView/sceneform-android/tree/master/samples/depth |
|
Hello, I seem to get an almost identical crash stack from a Unity AR app using the latest stable release of AR dependencies (4.2.3 - https://docs.unity3d.com/Packages/[email protected]/manual/index.html) The crash seems to happen about 1/5 play sessions |
|
I have the exact same crash when running the rawDepth sample on my Pixel 5 with Google Play Services for AR v1.31.221020293. |
|
I'm currently trying to create a minimal app that reproduces the problem. my crash looks like this: Crash Log@RGregat Does your log also write the following right after the crash report? I'm not even sure if it has todo with depth? I reduced the Update: It looks like just calling session.update() (with @Override
public void onDrawFrame(GL10 gl) {
if (session == null) {
return;
}
try {
session.update();
} catch (CameraNotAvailableException e) {
// Just ignore in this MRE
}
}Update 2: |
|
@wischi-chr the next time I encounter the crash I take a look, but the line looks very familiar to me. What you said is actually what I also have discovered, as soon as Depth is enabled I have a ticking bomb under the hood :) |
|
I believe I have the same error and can reproduce it with both 1.30 and 1.31, 1.29 does not seem to have that. This does not crash the app, but might be related. Here's the stacktrace, to make sure I'm actually reporting the same crash: This dump is from a personal app using sceneview, but the official hello_ar_kotlin example has the same crashdump. Hope this adds some data to bisect the issue. |
|
Hi all, first off, I'd like to apologize for how long it's taken to provide an adequate response. First of all, looking at the metrics, this crash seems to be rather rare; we were not able to create an environment that triggers this bug using any combination of the reported devices or any combination of configuration settings. Hopefully that can be some reassurance that your users aren't seeing this at a large scale. For 1.32 we've included some fix forwards that may resolve a potential issue that could resolve this. If you're on an affected device, could you please try hello_ar on the affected devices with a session configured with |
Cool, when can we expect the new version? |
|
Hi, |
|
Also note that it seems not to be reproductible with the 1.30.0 |
We have tested the new ARCore version with enabled PlaneFindingMode and the issue seems to be fixed. |
|
I have updated ARCore to 1.32.0 and disabled the PlaneFindingMode if the DepthMode is activated and so far an active session is way more stable than before! |
|
Thanks. May you give the full line of code and where it should be placed? The next update of ARCore will fix this issue so that we don't have to add this line? Thanks. |
@agGitHub Well I do nothing special, the settings for the DepthMode and PlaneFindingMode can be changed from everywhere. How you do it depends what you are using SceneForm, SceneView, directly ARCore or something else |
|
@devbridie so far I havn't had a native crash anymore with 1.33. I think we can close this issue for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@RGregat
Crash log
The text was updated successfully, but these errors were encountered: