New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Oculus] The app is closed after resuming the app from immersive mode and the crash dialog box is displayed after it's reopened #2017
Comments
https://tools.taskcluster.net/groups/NHmoIulEQQaf0W8PkuZbsw/tasks/NHmoIulEQQaf0W8PkuZbsw/runs/0/artifacts |
@Softvision-RemusDranca have you had a chance to test the above APKs? We would like to get this into master if it resolves the issue. |
I've verified this issue and it's no longer reproducible with the Firefox Reality 6 RC1 (a83b2bf) build. Now, the app is resumed in immersive mode. Tested on Oculus Quest and Oculus Go devices. |
The updated APKs can be found here: https://community-tc.services.mozilla.com/tasks/UIZHWWEAQvWSK7Fs4MrzHA |
I've retested this issue using the build provided in the above comment, on Oculus Quest Here are the results:
|
I think the problems after the app is quited are related to the restore issue, which was fixed in: #2181 I can't locally reproduce the perf issue (but I'm testing with the fix included) |
We've decided to hold off on landing the software rendering due to the high risk of changing at this point. If we see a lot of crash reports from v6 for this issue we can look at landing for v7 so we have more time to test it. |
I have verified this issue and it's no longer reproducible with the Firefox Reality version 7 RC3 (7b66fb1) build. Neither the Oculus Go, nor the Oculus Quest experienced any crashes, restarts or prompts and there was no noticeable difference in load time for websites afterwards for either resuming or quitting and reopening the app. |
[Notes]:
[Affected Versions]:
[Affected Platforms]:
[Prerequisites]:
[Steps to reproduce]:
[Expected results]:
[Actual results]:
[Additional Notes]:
The text was updated successfully, but these errors were encountered: