This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Firefox freezes after starting recording profile

davidxtejada
davidxtejada
more options

I am trying to use the profiler. I have added the button as stated in https://profiler.firefox.com/, but when I hit Start Recording Firefox completely freezes and I have to quit it. My OS is Ubuntu 20.04. I have tried with version 91 in a virtual machine and it works fine. Have also tried with version 93 in a virtual machine with Fedora 35 and even though it lets me start recording, the moment I hit stop it freezes.

I am trying to use the profiler. I have added the button as stated in https://profiler.firefox.com/, but when I hit Start Recording Firefox completely freezes and I have to quit it. My OS is Ubuntu 20.04. I have tried with version 91 in a virtual machine and it works fine. Have also tried with version 93 in a virtual machine with Fedora 35 and even though it lets me start recording, the moment I hit stop it freezes.

Chosen solution

I filed an issue in the Firefox Profiler GitHub and they were very helpful. Apparently it is an known bug, they offered a provisional solution in the issue linked, in case anybody runs into the same problem.

Read this answer in context 👍 1

All Replies (2)

Terry
Terry
more options

I had the same problem with 98.0.1 (Linux). I have removed the toolbar button and won't go near the app again.

davidxtejada
davidxtejada Question owner
more options

Chosen Solution

I filed an issue in the Firefox Profiler GitHub and they were very helpful. Apparently it is an known bug, they offered a provisional solution in the issue linked, in case anybody runs into the same problem.