Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

The crash dialog box is intermittently displayed after quitting from 360 videos and resuming the app #1959

Closed
Softvision-RemusDranca opened this issue Oct 11, 2019 · 11 comments
Assignees
Labels
[QA]:Normal issue Label for QA to mark normal issues logged [QA]:Verified fixed Label for QA to mark verified fixed issues
Milestone

Comments

@Softvision-RemusDranca
Copy link

[Affected Versions]:

  • Firefox Reality version 5-32821846 RC1 (58b59be)

[Affected Platforms]:

  • Oculus Quest - Android 7.1.1
  • HTC Vive Focus Plus - Android 7.1.2
  • Oculus Go - Android 7.1.2

[Prerequisites]:

  • The headset is turned on and the browser is opened.

[Steps to reproduce]:

  1. Open and Play a 360 video in immersive mode.
  2. Click the "Oculus/Vive" button from the controller.
  3. Click the "Quit/Home" button from the prompt displayed.
  4. Resume the app and observe the behavior.

[Expected results]:

  • The app is correctly resumed.

[Actual results]:

  • The crash dialog box is intermittently displayed.

[Additional Notes]:

  • This issue is not reproducible on the HTC Vive Focus and Lenovo Mirage Solo devices.
  • Attached are the log cat, crash report and a screed recording of the issue:
@Softvision-RemusDranca Softvision-RemusDranca added the [QA]:Major issue Label for QA to mark major issues logged label Oct 11, 2019
@jvonitter
Copy link
Contributor

The crash here is caused by a known Oculus bug, so we can't fix it right now. We could suppress the crash reports, but I would like to hold off doing that for now so we can collect the data. Since this only happens if you quit the app while in video immersive mode, the impact shouldn't be too bad.

I'm going to push this to 7 to revisit then.

@jvonitter jvonitter added this to the #7 polish milestone Oct 11, 2019
@Softvision-RemusDranca
Copy link
Author

Softvision-RemusDranca commented Oct 14, 2019

@jvonitter This issue is also reproducible on HTC Vive Focus Plus. I’m not sure if this will change the milestone set for it after taking this into consideration.
The attachments above are recorded with the HTC Vive Focus Plus device. I should have added the name of the device in front of them, sorry for possibly misleading you on this.

@bluemarvin
Copy link
Contributor

It's a bug in Android 7 which is unfortunately the version that most of the supported headsets are currently running. This is the same issue documented in #1770. I changed the way crashes are handled to prevent FxR from losing crash reports so now the user will be prompted with a crash dialog the next time they start FxR if it crashed on exit.

@Softvision-RemusDranca
Copy link
Author

@bluemarvin I've retested this scenario with the latest 6-32902155 (93816a5) build and it seems that after using the app for ~ one hour the issue is continuously reproducible.
Also, The HTC devices have ~ one minute where the screen is black until the app is resumed and the crash dialog is displayed and intermittently closes instead of resuming.
I've attached the videos and logcats tested with this build and I want you to confirm, if possible, that the same bug in Android 7 is causing this behavior or that I should log a new issue. Thanks in advance!

  • HTC Vive Focus Plus screen recording: link
  • HTC Vive Focus Plus logcat: link
  • HTC Vive Focus Plus crash report: link
  • Oculus Quest logcat: link
  • Oculus Quest crash report: link

@jvonitter
Copy link
Contributor

jvonitter commented Nov 25, 2019

@Softvision-RemusDranca or @Softvision-GeluHaiduc Can you check this one again? It may have been fixed by some other changes we did last week.

@Softvision-GeluHaiduc
Copy link

I managed to partially reproduce the issue using Firefox Reality version 7 RC3 (7b66fb1) installed on HTC Vive Focus Plus.
After more than 1 hour of stressing the app navigating Youtube and quitting and resuming the app creating tabs and windows, the app crashed, the logcat file is here and the crash report here.

@jvonitter
Copy link
Contributor

I think if it takes an hour and a lot of work to repro it, we can downgrade this from Major to Normal. I'll leave it open so we can investigate further.

@jvonitter jvonitter added [QA]:Normal issue Label for QA to mark normal issues logged and removed [QA]:Major issue Label for QA to mark major issues logged labels Nov 27, 2019
@jvonitter jvonitter modified the milestones: #7 polish, #8 features Nov 27, 2019
@MortimerGoro
Copy link
Contributor

MortimerGoro commented Nov 27, 2019

The latest crash report is different from the original one. We have already landed a fix for the latest crashlog (#2386)

If we cant reproduce the original one (https://crash-stats.mozilla.com/report/index/416d8ec1-66dd-4deb-8e9f-041c90191011) we could close this.

@jvonitter
Copy link
Contributor

Thanks @MortimerGoro! @Softvision-GeluHaiduc let us know if you can repro the original crash. If not, go ahead and close this issue.

@MortimerGoro
Copy link
Contributor

Fixed in #2482

@Softvision-RemusDranca Softvision-RemusDranca added the [QA]:Verified fixed Label for QA to mark verified fixed issues label Jan 20, 2020
@Softvision-RemusDranca
Copy link
Author

Softvision-RemusDranca commented Jan 20, 2020

I have verified this issue and it's no longer reproducible with the latest Firefox Realty 8 RC2 build (4ff1f59). I was able to reproduce this behavior only after stressing the app for a long period of time but not after resuming from 360 videos and I wasn't sure that the crashes are related so I opened a new issue, #2663, for tracking purpose.
Also I encountered issue #2675, which could block us from reproducing this issue but since this issue is intermittent it's safe to close it as verified fixed and log a new one if encountered in the future.

Tested on Oculus Go (Android 7.1.2), Oculus Quest (Android 7.1.1), HTC Vive Focus Plus (Android 7.1.2) and HTC Vive Focus (Android 7.1.2).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
[QA]:Normal issue Label for QA to mark normal issues logged [QA]:Verified fixed Label for QA to mark verified fixed issues
Projects
None yet
Development

No branches or pull requests

5 participants