Skip to content
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

In VR mode, ServoView constructor is called twice #22197

Closed
paulrouget opened this issue Nov 14, 2018 · 5 comments
Closed

In VR mode, ServoView constructor is called twice #22197

paulrouget opened this issue Nov 14, 2018 · 5 comments

Comments

@paulrouget
Copy link
Contributor

@paulrouget paulrouget commented Nov 14, 2018

Which leads to a panic (assert(DEFAULT_OPTION.is_null())).

I have no idea why the view is constructed twice.

@Manishearth
Copy link
Member

@Manishearth Manishearth commented Nov 14, 2018

Is this on oculus, or on googlevr too?

@paulrouget
Copy link
Contributor Author

@paulrouget paulrouget commented Nov 15, 2018

googlevr.

@Manishearth
Copy link
Member

@Manishearth Manishearth commented Nov 16, 2018

Hm, I'm not hitting this. What I get is:

  • visiting a page that uses vr lazy-loads googlevr, which causes the app to go back to the homepage (the brightness also seems to change, I think it's flickering really fast)

  • doing it again after the lazy load works. entering VR works sometimes (I sometimes get an error saying the app is compatible with Cardboard but not Daydream)

I'm not able to display to VR yet because of #22162

@paulrouget
Copy link
Contributor Author

@paulrouget paulrouget commented Nov 19, 2018

From Slack:


One thing that could affect is this: https://github.com/MozillaReality/FirefoxReality/blob/master/app/src/main/AndroidManifest.xml#L27

android:configChanges="density|keyboardHidden|navigation|orientation|screenSize|uiMode"

Check that you are using the same configChanges in the servo android manifest.xml

@paulrouget
Copy link
Contributor Author

@paulrouget paulrouget commented Nov 19, 2018

So Servo is (likely) destroyed and reloaded because of a change of config. I was wondering why this wasn't a problem with FxR. It's because FxR doesn't use servo arguments. Anyway, that should not be too hard to fix. Looking at it.

This was referenced Nov 21, 2018
bors-servo added a commit that referenced this issue Nov 22, 2018
Handle more config changes

Fix #22197

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/22246)
<!-- Reviewable:end -->
bors-servo added a commit that referenced this issue Nov 22, 2018
Handle more config changes

Fix #22197

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/22246)
<!-- Reviewable:end -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
@jdm @paulrouget @Manishearth and others
You can’t perform that action at this time.