Bugzilla

Hello,

Are you still able to reproduce this issue?

We would like to attempt to regress it, but we are unable due to hardware/software incompatibility. Unfortunately we do not have a Win11 with AMD GPU.
I have to ask you to help us by regressing it yourself, using a tool called mozregression. (https://mozilla.github.io/mozregression/)
Can you do that? I will write you a number of steps to take in order to do it correctly:

install mozregression:
a. Download this executable:
https://github.com/mozilla/mozregression/releases/download/5.0.0/mozregression-gui.exe
b. Instal the app.

You have to determine a build that reproduces the issue. You have already done that: Firefox 103.0 (64-bit), right? You can retest it anytime.
Then you should find one that does NOT reproduce it. Detailed steps:

a. Open Mozregression app;
b. Click "File" -> "Run a single build";
c. On the "Single Run Wizard" pop-up, "Basic configuration" page, change parameter "Build type" from "shippable" to "opt" and click "Next".
d. On the "Profile selection" page, just click the "Next" button.
e. On the "Build selection" page, change the "date" parameter to "release" by it's drop-down.
f. Then select a release number (numbers lower than 68 until you find one that does not reproduce the issue) on the from the drop-down on the left and click "Finish".
g. Now the mozregression app will open a firefox build of the selected release number and you can use it, close it and open another. (make a note of the version that does not reproduce the issue)
You will use mozregression app to "bisect" builds that reproduce the issue by builds that do not reproduce it in search of the one build/changeset that introduced the issue, in the first place:
a. Open mozregression-gui.exe
b. Click "File" -> "Run a new bisection"
c. On "Basic configuration" screen, select Build Type: "opt" and click "Next" button.
d. Skip "Profile selection" screen by the "Next" button.
e. On the Bisection wizard screen, you will need to select a build that reproduces the issue and one that does not:
e1. In the "Last known good build:" section, select "date" on the right drop-down and the date of the build you found NOT to reproduce the issue.
e2. In the "First known bad build:" section, select "date" on the right drop-down and the date of the build you found to reproduce the issue.
f. Click "Finish" to start the bisection process.
g. Builds will open one-by-one, you will need to test each one of them and see whether the issue reproduces. If it reproduces, then you need to select the "bad" button in the mozregression window and if not, you need to select the "good" button.
h. When bisection is done, you will have the information in the "Log View" section of the mozregression window; bisection may also fail due to not enough builds, but the logs can always be useful.

Copy the logs in a text file and attach it to this bug.

If there is still information you need regarding the regression process, please request information from me.
Thank you for your contribution!

Hello,

Are you still able to reproduce this issue?

We would like to attempt to regress it, but we are unable due to hardware/software incompatibility. Unfortunately we do not have a Win11 with AMD GPU.
I have to ask you to help us by regressing it yourself, using a tool called mozregression. (https://mozilla.github.io/mozregression/)
Can you do that? I will write you a number of steps to take in order to do it correctly:

install mozregression:
a. Download this executable:
https://github.com/mozilla/mozregression/releases/download/5.0.0/mozregression-gui.exe
b. Install the app.

You have to determine a build that reproduces the issue. You have already done that: Firefox 103.0 (64-bit), right? You can retest it anytime.
Then you should find one that does NOT reproduce it. Detailed steps:

a. Open Mozregression app;
b. Click "File" -> "Run a single build";
c. On the "Single Run Wizard" pop-up, "Basic configuration" page, change parameter "Build type" from "shippable" to "opt" and click "Next".
d. On the "Profile selection" page, just click the "Next" button.
e. On the "Build selection" page, change the "date" parameter to "release" by it's drop-down.
f. Then select a release number (numbers lower than 68 until you find one that does not reproduce the issue) on the from the drop-down on the left and click "Finish".
g. Now the mozregression app will open a firefox build of the selected release number and you can use it, close it and open another. (make a note of the version that does not reproduce the issue)
You will use mozregression app to "bisect" builds that reproduce the issue by builds that do not reproduce it in search of the one build/changeset that introduced the issue, in the first place:
a. Open mozregression-gui.exe
b. Click "File" -> "Run a new bisection"
c. On "Basic configuration" screen, select Build Type: "opt" and click "Next" button.
d. Skip "Profile selection" screen by the "Next" button.
e. On the Bisection wizard screen, you will need to select a build that reproduces the issue and one that does not:
e1. In the "Last known good build:" section, select "date" on the right drop-down and the date of the build you found NOT to reproduce the issue.
e2. In the "First known bad build:" section, select "date" on the right drop-down and the date of the build you found to reproduce the issue.
f. Click "Finish" to start the bisection process.
g. Builds will open one-by-one, you will need to test each one of them and see whether the issue reproduces. If it reproduces, then you need to select the "bad" button in the mozregression window and if not, you need to select the "good" button.
h. When bisection is done, you will have the information in the "Log View" section of the mozregression window; bisection may also fail due to not enough builds, but the logs can always be useful.

Copy the logs in a text file and attach it to this bug.

If there is still information you need regarding the regression process, please request information from me.
Thank you for your contribution!