Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reasons for "Disabled Features" not Documented #5373

Open
grnnja opened this issue Feb 17, 2025 · 1 comment
Open

Reasons for "Disabled Features" not Documented #5373

grnnja opened this issue Feb 17, 2025 · 1 comment

Comments

@grnnja
Copy link

grnnja commented Feb 17, 2025

Hi.

I would like to do memory profiling but it is under "Disabled Features" and I can't check the check boxes to enable them.

Image

There is no stated reason for why memory tracking is disabled and the docs don't mention anything either.

https://profiler.firefox.com/docs/#/

If someone could tell me why they are disabled that would be helpful. thanks

┆Issue is synchronized with this Jira Task

@fqueze
Copy link
Contributor

fqueze commented Feb 18, 2025

There is no stated reason for why memory tracking is disabled and the docs don't mention anything either.

I agree it would be nicer if the reason for a feature being disabled was explained in about:profiling. Or if the features that don't make any sense on your platform were completely hidden, rather than disabled (Java is android-only, "No Timer Resolution Change" is a Windows thing).

If someone could tell me why they are disabled that would be helpful. thanks

Native allocations tracking is enabled on Nightly builds and early beta builds.

Memory tracking used to be the same, but starting with Firefox 136 (with the work that happened in https://bugzilla.mozilla.org/show_bug.cgi?id=1806054) it might be available on release builds too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants