false startup with MOZ_PROFILER_STARTUP=1
Categories
(Core :: Gecko Profiler, defect, P3)
Tracking
()
People
(Reporter: pzz, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:96.0) Gecko/20100101 Firefox/96.0
Steps to reproduce:
run Nightly all day.
dismiss the offer to reboot the new version.
exit from window manager (thus xorg shuts down).
boot up.
launch lxqt, and xterm.
MOZ_PROFILER_STARTUP=1 /opt/firefox/firefox
Actual results:
consistently every morning, Nightly runs for about 2 seconds, about as long as passes before the "updating Nightly" progress meter appears, then exits, having shown no window, no dialog, no progress meter, nor any standard nor error output. exit status is 0.
relaunch again:
MOZ_PROFILER_STARTUP=1 /opt/firefox/firefox
and it works.
Expected results:
it should work the first time. or maybe give a clue why not.
|
||
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
||
Updated•4 years ago
|
Or sometimes, during that brief 2 second lifespan, there is some output, eg:
Profiling timer expired
|
||
Comment 3•3 years ago
|
||
(In reply to gregrwm from comment #2)
Or sometimes, during that brief 2 second lifespan, there is some output, eg:
Profiling timer expired
This seems to be the default handling of the SIGPROF signal.
I wonder if it's possible that somehow in the case of restarting for an update the profiler isn't correctly uninitialized.
Description
•