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

Only a single isolate shown in isolate picker when multiple are running #8561

Open
elliette opened this issue Nov 26, 2024 · 1 comment
Open
Labels
cross-screen Issues that affect multiple DevTools screens, i.e. shared functionality and widgets P2 important to work on, but not at the top of the work list. screen: memory Issues with the Memory screen.

Comments

@elliette
Copy link
Member

Paraphrased from Discord discussion about memory panel (@srawlins report):

"There are two isolates running, but I only see one in the isolate picker. Observatory shows several isolate groups, and I see the system isolate group, which the primary DAS code seems to run in. And then my "plugin" isolate group, which is what I'm looking for. (The primary isolate in that isolate group appears to be also called "main.""

@elliette elliette added screen: memory Issues with the Memory screen. P2 important to work on, but not at the top of the work list. cross-screen Issues that affect multiple DevTools screens, i.e. shared functionality and widgets labels Nov 26, 2024
@srawlins
Copy link
Contributor

Thanks @elliette ; yeah in case it helps to distinguish: in Observatory I see ~4 isolate groups, and I am trying to navigate to the "main" (is that right?) isolate in another group, spawned from a URI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cross-screen Issues that affect multiple DevTools screens, i.e. shared functionality and widgets P2 important to work on, but not at the top of the work list. screen: memory Issues with the Memory screen.
Projects
None yet
Development

No branches or pull requests

2 participants