Esta página ainda não está no seu idioma. Está a ler o texto em inglês.
Knowledge base
Already many profiles are open. Close one before opening another
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 under Browsers at once.
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.
Windows already open are left alone
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 from the Support screen. The report that travels with the message carries the system, the memory and the chosen ceiling, which is exactly what this refusal is computed from.
What this article does not cover
- The daily pace of actions inside a profile. The app counts those and warns you, and it 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.
Still stuck
Support reads the report that travels with your message and answers with the cause, not with a checklist.