Bugzilla

This is not so easy to debug.
Since this morning, Firefox is crashing at startup with one of my profiles (it is *not* crashing with another profile I have).
Using mozregression, I've noticed builds from a few days ago crash too, which rules out a Firefox change. Using very old builds, I have found the crash to start since https://hg.mozilla.org/integration/autoland/rev/96732a2f2846c158ac1c1dc9f1f2f9b1d676df83.

This means something changed on my system that caused Firefox to start failing, and only with this profile.
Here's the list of packages I upgraded yesterday:
```
2022-06-14 01:53:24 upgrade clang-15:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:24 upgrade libclang-common-15-dev:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:27 upgrade python3-lldb-15:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:27 upgrade liblldb-15:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:28 upgrade lldb-15:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:28 upgrade llvm-15-dev:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:37 upgrade libclang-cpp15:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:39 upgrade libllvm15:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:43 upgrade llvm-15:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:45 upgrade llvm-15-runtime:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:45 upgrade llvm-15-linker-tools:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:46 upgrade llvm-15-tools:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:46 upgrade libclang1-15:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:47 upgrade libglib2.0-dev:amd64 2.72.1-1 2.72.2-2
2022-06-14 01:53:48 upgrade libglib2.0-dev-bin:amd64 2.72.1-1 2.72.2-2
2022-06-14 01:53:49 upgrade libglib2.0-bin:amd64 2.72.1-1 2.72.2-2
2022-06-14 01:53:49 upgrade libglib2.0-0:amd64 2.72.1-1 2.72.2-2
2022-06-14 01:53:49 upgrade libglib2.0-0:i386 2.72.1-1 2.72.2-2
2022-06-14 01:53:50 upgrade libglib2.0-data:all 2.72.1-1 2.72.2-2
2022-06-14 01:53:51 upgrade eog:amd64 42.1-1 42.2-1
2022-06-14 01:53:52 upgrade gdal-data:all 3.4.3+dfsg-1 3.5.0+dfsg-1
2022-06-14 01:53:52 upgrade gnome-maps:amd64 42.1-1 42.2-1
2022-06-14 01:53:53 upgrade libnftnl11:amd64 1.2.1-1 1.2.2-1
2022-06-14 01:53:53 upgrade libsdl2-2.0-0:amd64 2.0.22+dfsg-4 2.0.22+dfsg-5
2022-06-14 01:53:53 upgrade libsdl2-2.0-0:i386 2.0.22+dfsg-4 2.0.22+dfsg-5
2022-06-14 01:53:54 upgrade linux-compiler-gcc-11-x86:amd64 5.17.3-1 5.18.2-1
2022-06-14 01:54:00 upgrade linux-headers-amd64:amd64 5.17.3-1 5.18.2-1
2022-06-14 01:54:10 upgrade linux-image-amd64:amd64 5.17.3-1 5.18.2-1
2022-06-14 01:54:10 upgrade linux-libc-dev:amd64 5.17.3-1 5.18.2-1
2022-06-14 01:54:11 upgrade network-manager-gnome:amd64 1.26.0-1 1.28.0-1
```

Which makes me think this is due to the recent kernel upgrade.
It must also be due to something specific in my profile, given that I can't reproduce in a clean profile or other "dirty" profiles I have.

This is not so easy to debug.
Since this morning, Firefox is hanging at startup with one of my profiles (it is *not* hanging with another profile I have).
Using mozregression, I've noticed builds from a few days ago fail too, which rules out a Firefox change. Using very old builds, I have found the hang to start since https://hg.mozilla.org/integration/autoland/rev/96732a2f2846c158ac1c1dc9f1f2f9b1d676df83.

This means something changed on my system that caused Firefox to start failing, and only with this profile.
Here's the list of packages I upgraded yesterday:
```
2022-06-14 01:53:24 upgrade clang-15:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:24 upgrade libclang-common-15-dev:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:27 upgrade python3-lldb-15:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:27 upgrade liblldb-15:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:28 upgrade lldb-15:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:28 upgrade llvm-15-dev:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:37 upgrade libclang-cpp15:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:39 upgrade libllvm15:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:43 upgrade llvm-15:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:45 upgrade llvm-15-runtime:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:45 upgrade llvm-15-linker-tools:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:46 upgrade llvm-15-tools:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:46 upgrade libclang1-15:amd64 1:15~++20220609101129+f8144700ebc9-1~exp1~20220609221215.550 1:15~++20220613111440+aebe24a856d2-1~exp1~20220613111528.557
2022-06-14 01:53:47 upgrade libglib2.0-dev:amd64 2.72.1-1 2.72.2-2
2022-06-14 01:53:48 upgrade libglib2.0-dev-bin:amd64 2.72.1-1 2.72.2-2
2022-06-14 01:53:49 upgrade libglib2.0-bin:amd64 2.72.1-1 2.72.2-2
2022-06-14 01:53:49 upgrade libglib2.0-0:amd64 2.72.1-1 2.72.2-2
2022-06-14 01:53:49 upgrade libglib2.0-0:i386 2.72.1-1 2.72.2-2
2022-06-14 01:53:50 upgrade libglib2.0-data:all 2.72.1-1 2.72.2-2
2022-06-14 01:53:51 upgrade eog:amd64 42.1-1 42.2-1
2022-06-14 01:53:52 upgrade gdal-data:all 3.4.3+dfsg-1 3.5.0+dfsg-1
2022-06-14 01:53:52 upgrade gnome-maps:amd64 42.1-1 42.2-1
2022-06-14 01:53:53 upgrade libnftnl11:amd64 1.2.1-1 1.2.2-1
2022-06-14 01:53:53 upgrade libsdl2-2.0-0:amd64 2.0.22+dfsg-4 2.0.22+dfsg-5
2022-06-14 01:53:53 upgrade libsdl2-2.0-0:i386 2.0.22+dfsg-4 2.0.22+dfsg-5
2022-06-14 01:53:54 upgrade linux-compiler-gcc-11-x86:amd64 5.17.3-1 5.18.2-1
2022-06-14 01:54:00 upgrade linux-headers-amd64:amd64 5.17.3-1 5.18.2-1
2022-06-14 01:54:10 upgrade linux-image-amd64:amd64 5.17.3-1 5.18.2-1
2022-06-14 01:54:10 upgrade linux-libc-dev:amd64 5.17.3-1 5.18.2-1
2022-06-14 01:54:11 upgrade network-manager-gnome:amd64 1.26.0-1 1.28.0-1
```

Which makes me think this is due to the recent kernel upgrade.
It must also be due to something specific in my profile, given that I can't reproduce in a clean profile or other "dirty" profiles I have.