FirefoxReality VS profiler

Used to use Firefox VR but since it’s discontinued I now use Wolvic from AppLab. There’s a curved screen option in the display settings that I recommend turning on if it isn’t by default and then you can just resize the screen to whatever size you want. Another tip would be that you can install custom skyboxes like this one by simply dropping the files in the correct directory through Sidequest, works exactly the same for Wolvic and Firefox. I love reading in space :)

This is really interesting. Last night I was looking at FireFox Reality's repo and was pleasantly surprised to see [some newer commits][1]. Now today I see that Wolvic is [a fork of FireFox Reality][2] and that the commits were contributed from that project. I'm happy to see a private company fund new work on this front.

[1]: https://github.com/MozillaReality/FirefoxReality/commits/mai...

The last time Firefox tried to migrate to an emerging platform (Boot to Gecko), they abandoned the project. It was forked and found success as KaiOS.

I wonder if history will repeat itself here with Wolvic. Firefox Reality was last released in 2020, and I've heard it's not good compared to the Chromium-based Oculus Browser.

https://github.com/MozillaReality/FirefoxReality/releases

https://github.com/MozillaReality/FirefoxReality I would guess

The last project that I looked into was Firefox Reality (GitHub)

I was also annoyed by Firefox Reality's inability to handle intents from other applications (doesn't appear in "Open with" picker). (see issue: https://github.com/MozillaReality/FirefoxReality/issues/3924)

There is an issue reported here, but no response from the devs yet https://github.com/MozillaReality/FirefoxReality/issues/3924

Probably your best bet is to use the Firefox Profiler once it starts hogging the CPU to try to see what it's doing. I'd be happy to take a look at the result although I don't have a lot of experience at diagnosing performance problems; hopefully the profile will make it obvious what's going on.

I tried using the https://profiler.firefox.com/ and running with:

You can try to reproduce while taking a profile using the Firefox profiler, then share it in the #perf:mozilla.org room on Mozilla's Matrix instance.

Run a profiling session for ~30 sec when you notice something is running slower than you expect, see https://profiler.firefox.com/. Share results here if you want help interpreting them.

Next time, send a SIGABRT to the main process (kill -6 $(pidof firefox)) and use the resulting backtrace (you will find a link to the crash report in about:crashes) to file a bug. A performance profile could be useful, but you'll need to know first what to capture. This seems like a graphics issue, so try the Graphics preset. Share a link to your report.

https://profiler.firefox.com will be useful if you can capture and share it to developers.

If you can reproduce it in safe mode and a clean profile, capture a performance profile using the clean profile while trying to load a problematic webpage, don't remove any information from it, and share it here (although it's typically not easy for users to analyse them), or file a bug with it attached.

Next time, capture a performance profile using the Graphics preset, and kill the browser by entering kill -6 $(pidof firefox) in a shell. This will create a bug report (unless debian disables the crash reporter) that would indicate where Firefox is stuck at. You might need to use an official build to get useful results.