Making sure Loop complies with Firefox system requirements

RESOLVED INVALID

Status

Hello (Loop)
Client
RESOLVED INVALID
4 years ago
4 years ago

People

(Reporter: RT, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
Users report performance issues with Loop through input.mozilla.org (crashing Firefox, slow performance, RAM use (.8-1.5GB), video tiling, ...).

Part of the testing process do we ensure that Loop complies with the Firefox system requirements - https://www.mozilla.org/en-US/firefox/32.0.3/system-requirements/ ?
In my experience the types of issues you're citing tend to be very user specific and would not be caught through testing unless they were extremely common and widespread. That said, I'm having a hard time finding evidence to support the idea that performance is a widespread issue.

Here's what I found for the last month[1]:
* 1 report mentioning the word "crash"
* 1 report mentioning the word "slow"
* 0 reports mentioning the word "hang"
* 87 reports mentioning the word "quality"
* 334 reports mentioning the word "disconnect"

It seems like most people are complaining about "disconnect" issues (bug 1074517?) and an extreme minority are have performance/stability issues. My suggestion would be to work with the User Advocacy team to see if there are specific common complaints we could be investigating and to tackle them individually in separate bug reports.

Note that while we have performance tests that warn us of regressions, we don't tend to do testing to ensure a particular feature is conforming to our system requirements. In actuality, I think the system requirements are reviewed from time to time to make sure they reflect the reality of the product, not the other way around.

1. https://input.mozilla.org/en-US/?product=Loop&happy=0
(Reporter)

Comment 2

4 years ago
Thanks for the clarifications on the process.
If testing to ensure a feature conforms with system requirements is not the way we handle system requirements compliance then this bug should be closed.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.