Moved from https://github.com/firefox-devtools/Gecko-Profiler-Addon/issues/96.

This was an issue with the add-on, and is still affecting the new popup. The STR mostly reproduces, all you have to do it have an open private browsing window, and it doesn't react. The DevTools panel handles this case correctly and displays a message.

mconley wrote:

STR:

• Turn the profiler add-on off.
• Open up a private browsing window
• Switch back to the original normal browsing window
• Attempt to start the profiler.

ER:

At least for some folks, they might expect the profiler to start.

AR:

The profiler doesn't start. Clicking "Start" in the profiler action panel does nothing.

I understand why we're not starting the profiler - we don't want to collect potentially sensitive data from a PB window. We should, however, probably make it clear that this is why enabling the profiler isn't possible.

It seems like this works now - possibly due to fixing bug 1639716? Can this be marked resolved?

This is correct. Thanks!