Bug 1800749 Comment 8 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Okay, I've run it again today and managed to reproduce the assertion! I had to follow some more specific steps. There's a confounding Windows build issue that makes this trickier, since solved, in Bug 1800462. In my previous attempts, I had just used a slightly later revision, hoping it'd work out the same. I also was placing prefs.js in the nightly profile folder, hoping that would work, whereas I'm not using `--prefs` to specify the file. My exact steps were:

```bash
hg up 8495494c57f8
hg backout -r 6b9175bbaba8995fc54eb3da9837cc83b14741fc # back out the revision that causes local build failures
./mach clobber
./mach configure --enable-debug --enable-fuzzing
./mach build
pip install fuzzfetch grizzly-framework
rm -rf firefox/ # not sure if this is relevant, but my firefox folder already existed, so I removed it first then ran fuzzfetch
python -m fuzzfetch -d --fuzzing -n firefox
python -m grizzly.replay --prefs /c/prefs.js ./firefox/firefox.exe testcase.html
```

The final command gives me:
```
Result: Assertion failure: value > 0, at /builds/worker/checkouts/gecko/accessible/generic/LocalAccessible.cpp:3579
```
Okay, I've run it again today and managed to reproduce the assertion! I had to follow some more specific steps. There's a confounding Windows build issue that makes this trickier, since solved, in Bug 1800462. In my previous attempts, I had just used a slightly later revision, hoping it'd work out the same. I also was placing prefs.js in the nightly profile folder, hoping that would work, whereas I'm not using `--prefs` to specify the file. My exact steps were:

```bash
hg up 8495494c57f8
hg backout -r 6b9175bbaba8995fc54eb3da9837cc83b14741fc # back out the revision that causes local build failures
./mach clobber
./mach configure --enable-debug --enable-fuzzing
./mach build
pip install fuzzfetch grizzly-framework
rm -rf firefox/ # not sure if this is relevant, but my firefox folder already existed, so I removed it first then ran fuzzfetch
python -m fuzzfetch -d --fuzzing -n firefox
python -m grizzly.replay --prefs /c/prefs.js ./firefox/firefox.exe testcase.html
```

The final command gives me:
```
Result: Assertion failure: value > 0, at /builds/worker/checkouts/gecko/accessible/generic/LocalAccessible.cpp:3579
```

(also, side note, I don't seem to have pernosco access yet. I tried accessing it via my personal github - https://github.com/nmlapre - but don't have authorization to view the stack trace)
Okay, I've run it again today and managed to reproduce the assertion! I had to follow some more specific steps. There's a confounding Windows build issue that makes this trickier, since solved, in Bug 1800462, that affects this specific revision. In my previous attempts, I had just used a slightly later revision, hoping it'd work out the same. I also was placing prefs.js in the nightly profile folder, hoping that would work, whereas I'm not using `--prefs` to specify the file. My exact steps were:

```bash
hg up 8495494c57f8
hg backout -r 6b9175bbaba8995fc54eb3da9837cc83b14741fc # back out the revision that causes local build failures
./mach clobber
./mach configure --enable-debug --enable-fuzzing
./mach build
pip install fuzzfetch grizzly-framework
rm -rf firefox/ # not sure if this is relevant, but my firefox folder already existed, so I removed it first then ran fuzzfetch
python -m fuzzfetch -d --fuzzing -n firefox
python -m grizzly.replay --prefs /c/prefs.js ./firefox/firefox.exe testcase.html
```

The final command gives me:
```
Result: Assertion failure: value > 0, at /builds/worker/checkouts/gecko/accessible/generic/LocalAccessible.cpp:3579
```

(also, side note, I don't seem to have pernosco access yet. I tried accessing it via my personal github - https://github.com/nmlapre - but don't have authorization to view the stack trace)
Okay, I've run it again today and managed to reproduce the assertion! I had to follow some more specific steps. There's a confounding Windows build issue that makes this trickier, since solved, in Bug 1800462, that affects this specific revision. In my previous attempts, I had just used a slightly later revision, hoping it'd work out the same. I also was placing prefs.js in the nightly profile folder, hoping that would work, whereas now I'm using `--prefs` to specify the prefs file. My exact steps were:

```bash
hg up 8495494c57f8
hg backout -r 6b9175bbaba8995fc54eb3da9837cc83b14741fc # back out the revision that causes local build failures
./mach clobber
./mach configure --enable-debug --enable-fuzzing
./mach build
pip install fuzzfetch grizzly-framework
rm -rf firefox/ # not sure if this is relevant, but my firefox folder already existed, so I removed it first then ran fuzzfetch
python -m fuzzfetch -d --fuzzing -n firefox
python -m grizzly.replay --prefs /c/prefs.js ./firefox/firefox.exe testcase.html
```

The final command gives me:
```
Result: Assertion failure: value > 0, at /builds/worker/checkouts/gecko/accessible/generic/LocalAccessible.cpp:3579
```

(also, side note, I don't seem to have pernosco access yet. I tried accessing it via my personal github - https://github.com/nmlapre - but don't have authorization to view the stack trace)

Back to Bug 1800749 Comment 8