When the browser closes by itself

While a profile is open, its tabs go into memory once every half minute. A profile that is closed is left alone.

On the built-in engine those are its own windows; on ARMANOS Browser it is the local port automation already uses. A browser that cannot answer says nothing, so the memory you had stays.

The half-minute snapshot is not counted as a change you made.

It also stays on this computer. The fields that travel to your account are named one by one, and open page addresses are not among them.

• The change date stays put

  It moves only for what you did to the profile.

• Nothing new means nothing written

  Tabs that have not moved since last time are not written to disk twice.

• An empty answer keeps the memory

  A browser still starting, or reloading a page, does not erase what it held a minute ago.

A browser that exits with a code nobody asked for, or dies on a signal, has crashed. Pressing stop is not that, nor is closing the window yourself.

The last list of tabs stays untouched until you answer: a launch does not write over it. Only a fresh crash of the same profile records it anew.

• The notification names the profile

  From it you land on the profile in question, and you see how many tabs were remembered when the engine named no reason.

• The reason, when the engine gave one

  A line the browser managed to print before dying is what you read, in place of the tab count.

• One message per profile per clock hour

  A browser crashing in a loop folds into the message still sitting unread, instead of burying the rest under copies of itself.

• When nothing was seen nothing is promised

  If the snapshot was empty, and the engine named no reason, the message says the profile and its cookies are intact and stops there.

The question comes before the browser starts, because your answer decides what it opens with. It shows the profile, the time its browser went and how many tabs were remembered.

1. 1

   Bring them back

   The tabs open again.

2. 2

   Start with a clean slate

   A first refusal only puts the question off. Refuse a second time without closing the app window and the tabs are dropped for good.

3. 3

   Either way the profile opens

   The question decides the tabs and nothing else about the launch.

On ARMANOS Browser they queue behind the other tabs of the launch.

The built-in engine has no tab strip, so each one comes back as its own window.

• The same folder

  Cookies and storage are the ones that profile already had.

• The same way out

  A restored window leaves through the profile's proxy like every other window of it.

• Only after a launch that worked

  A launch that fails keeps both the tabs and the offer to bring them back.

A browser is not the only thing that can be cut off mid sentence. Three more loose ends are picked up for you at every start.

• A session swap caught in half

  A profile stuck between the two renames of a session move comes back to you on the older copy, because the newer one may never have finished being written.

• A tunnel that outlived the app

  On macOS and Linux a tunnel to your server that outlived ARMANOS is closed behind you, and an ssh of somebody else's is left alone.

• Folders from a run that was killed

  Tunnel folders and working leftovers from a previous run are cleared behind you, because otherwise they pile up until the disk has no room for a profile.