Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Gecko Profiler 0.17 fails to start with Firefox 55.0.3 on FreeBSD

See original GitHub issue

The Start button is present but when it’s clicked, profiling does not start.

2017-09-09 06 40 09

[grahamperrin@momh167-gjp4-hpelitebook8570p-freebsd] ~% date ; uname -v
Sat  9 Sep 2017 06:55:19 BST
FreeBSD 12.0-CURRENT #0 r320869: Mon Jul 10 13:57:55 UTC 2017     root@releng3.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC 
[grahamperrin@momh167-gjp4-hpelitebook8570p-freebsd] ~% pkg info firefox | grep -i version
Version        : 55.0.3_1,1
[grahamperrin@momh167-gjp4-hpelitebook8570p-freebsd] ~%

Issue Analytics

State:
Created 6 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

2reactions

jbeichcommented, Nov 2, 2017

PROFILE=on just passes --enable-profiling which predates GeckoProfiler. FreeBSD can still use external profilers like pmcstat(8) or dtrace(1) which don’t like -fomit-frame-pointer inherited from --enable-optimize.

1reaction

mstangecommented, Sep 9, 2017

Does that imply that profiling can not be implemented even when Gecko Profiler (the extension) is installed and enabled?

That’s correct. Most of the Gecko profiler C++ code is disabled on BSD at the build level, because important parts are not implemented for that platform. Most notably, we’re missing BSD variants of platform-*.cpp and shared-libraries-*.cc. Here are the Linux variants of those files: platform-linux-android.cpp shared-libraries-linux.cc