Here's what I found while triaging this issue:

This reads as a Linux-specific profiling support request rather than a user-facing bug report. The current issue body is too sparse to tell which profiling mode or output behavior is intended.

I have a few follow-up questions before I can narrow this down:

Should this enable the existing heap-usage tracking/jemalloc pprof flow on Linux, the DHAT or CPU profiling feature paths, or a different profiling mechanism?
Should Linux profiles be uploaded automatically when high memory usage is detected, or only written locally/on demand?

Reply in-thread with those details and the triage workflow will automatically re-evaluate the issue and update the diagnosis, labels, and next steps.

Maintainer details

I concluded that linux profiling support appears to be an underspecified enhancement request, with current code suggesting heap/pprof profiling is only partially wired outside macOS..

Triage summary

This looks like a Linux-specific enhancement request to enable Warp profiling. The issue is currently under-specified because it only links Linear APP-4325 and does not say which profiling mode, trigger, or output behavior should be supported.

Evidence from current code

app/src/profiling.rs has several feature-gated profiling paths: pprof_cpu_profiling, dhat_heap_profiling, jemalloc_auto_heap_profiling, jemalloc_pprof, and heap_usage_tracking.
The heap-profile upload flow shells out to a pprof helper, but pprof_binary_path() currently supports macOS only and returns unsupported on other platforms.
script/macos/bundle enables jemalloc_pprof,heap_usage_tracking for dev/preview and bundles pprof when heap usage tracking is enabled.
script/linux/bundle currently enables jemalloc_pprof for dev builds only, and does not enable heap_usage_tracking or bundle a Linux pprof helper.
app/src/system/info.rs only triggers automatic heap-profile dumping when heap_usage_tracking is compiled in.

Duplicate check

Searched all open issues. #9754 is a near-exact title match, and #5155 is a broader profiling request. I am not marking this as a duplicate because only one existing issue is a strong duplicate candidate; #5155 appears related but broader.

Suggested next step

Clarify the intended Linux profiling mode and output/trigger so this can be routed to the performance/platform implementation path.

Question reasoning

Should this enable the existing heap-usage tracking/jemalloc pprof flow on Linux, the DHAT or CPU profiling feature paths, or a different profiling mechanism? — The codebase has multiple profiling implementations behind different Cargo features, and the title does not specify which one this issue is meant to enable.
Should Linux profiles be uploaded automatically when high memory usage is detected, or only written locally/on demand? — The current macOS-oriented heap profiling path uploads to Sentry after a memory threshold, while other profiling paths write local artifacts; implementation depends on the expected output behavior.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Enable Profiling on Linux #9753

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions