IssueTracker

Actually I believe it would throw a runtime error, not just be redundant:

if (mRecycled) {
            throw new RuntimeException(toString() + " recycled twice!");
        }

Internal note: looks related to Change I39727bc67

This will be fixed by Change I9baebec66991dd308edda2ce66f1225d25037644 in an upcoming release.

Thank you for the report!

Regarding reproducing what I said in comment #2: Just run the same app in 3 emulators at once, and press the button in each emulator. Note the large number of processes in the Database Inspector process list, and the difficulty of finding a particular process, and, even worse, the difficulty of switching around between all these processes during debugging. Every switch means finding the right process in the huge list again.

Peter, David, could you please take a look at this one?

Adarsh / Chris, you may want to weigh in, but for me, my takeaway is we should sort process name in the pulldown list

I agree, though overall I'd like to redesign the process picker because just sorting doesn't address the scale issue when you have many devices + many processes. We've gotten similar feedback with Layout Inspector and Profiler as well.

I have a design proposal in mind - I just have to sketch it. Maybe we can push to get this done for 4.1!

I think, as a minimum, we should sort the list. Very curious about Chris's long-term solution, though! Is the process picker a re-usable component? Or does each team implement it differently?

I'm guessing we won't get a redesign done in time for 4.1 - we're probably going to lean on a standard IntelliJ component, and changing to our own UI component may be time consuming.

Ideally a reusable component should be designed since we need it for various scenarios. I can't speak to the implementation of the current process pickers.

For IntelliJ, they just have a dropdown menu or combo box which is what we are using. If/when we get this new picker done, it'd be worth upstreaming it to them I think.

Yes! I'm all for a new reusable component. I was just dubious about the 4.1 timeframe.

Fair enough on 4.1 ;)

Regarding comment #14: I do see that there is some sorting happening around preferred and non-preferred processes, and I think this can be helpful in principle. The mask to match preferred processes needs to also match other processes of the same app, not just a single process, that's part of the problem.

In short: consider both a.b.c.d and a.b.c.d:extproc preferred processes. They belong to the same app a.b.c.d

Cool - good to know these details to consider in the design!

Fix pending.

Nice - thank you!

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Studio Jellyfish | 2023.3.1 Canary 1
• Android Gradle Plugin 8.4.0-alpha01

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!