Already many profiles are open. Close one before opening another

This is a refusal to open one more, never a shutdown of what is already running. The number in the line is how many profiles are open at this second, and the ceiling it ran into is computed from the memory in this machine.

The number is how many are open

The line names the count open right now, not the ceiling. Reading it as the ceiling sends you looking for a window that is not there.

The ceiling itself sits on the Engine screen, in the Browsers at once field.

Where the ceiling comes from

It is computed from the memory this computer reports, leaving several gigabytes to the system and about one to each browser. It never falls below four and never rises above thirty two.

So eight gigabytes gives about five, and a workstation with sixty four gives far more.

The Browser engine screen: the Browsers at once setting stands at the value worked out from the memory this computer reports. — Browsers at once on a machine where that works out to five. The line beside it says the refusal stops the next window and leaves the open ones alone.

Windows already open are left alone

Nothing you have running is closed. The app declines the next one and stops there, and the profiles on screen keep their sessions.

Raise it yourself

Browsers at once takes a number of your own and keeps it, inside the same floor of four and ceiling of thirty two.

Put it back to the automatic value and the limit follows the hardware again, which matters when you move to another machine.

Queues wait instead of failing

A bulk launch, a flow run and a schedule do not write a profile off when there is no room. They wait for a slot for up to half an hour.

A night warm-up of thirty profiles therefore finishes on a machine that holds five at a time.

An open profile is counted once

Pressing start on a profile that already runs does not meet the ceiling at all. The app brings the window forward instead of counting a second copy.

Collecting the evidence

If the count in the line does not match the windows you can see, note the number and reproduce it once more.

Write through Help → Write to support. The report that travels with the message carries the system and the app version, but not the machine's memory or the number in Browsers at once, so name those in the message yourself.

What this article does not cover

Safe pace inside a profile. It counts pages opened, not actions, and only advises, never steps in.
A profile that will not open while nothing else is running. The line there is different.
How much memory each browser really takes. The ceiling is an estimate made before anything opens.

Where this is decided

Each number above is one place in the code and one stand.

The ceiling is computed from memory and held between four and thirty two: apps/desktop/test/предел-открытых.js
A slot is taken by a counter so two launches of one profile do not free it early: apps/desktop/test/место-берётся-счётчиком.js
The bulk queue waits for a slot instead of writing the profile off: apps/desktop/test/очередь-запуска.js
A flow run waits for a slot on the same rule: apps/desktop/test/сценарий-ждёт-места.js

Questions

Does closing a window free a slot at once?: Yes. The count is taken at the moment of the next launch, not on a timer.
Why is four the floor?: Below four the product stops being useful for the work people buy it for, and a machine that cannot hold four browsers will struggle with one.
Does a profile with no window count?: Yes. It is a full browser without a window on screen, and it costs the same memory as one with a window.

Next to this

Still stuck

Support answers with the cause, not with a checklist.

Contact support Knowledge base