Concurrent runs of multiple instances of the same version of Waterfox Current

[grahamperrin]

From #1211 (comment) for builds 20191015002329 (Classic) and 20191015121210 (Current) on KDE Plasma in Manjaro Linux:

… both applications appear as a single task in Task Manager: …

Also, it's possible to run two instances of a single version of Waterfox Current – if the builds differ.

As far as I can tell there's no risk to user data – profiles are separate – so (exotically) this may be viewed as a feature, not a bug.

Initial discovery:

• 2019-10-26 08:40 concurrent run of two builds of Waterfox Current 2019.10 as a single task.zip
• https://put.re/player/Y9zKvdEh.mp4

A more focused view:

• 2019-10-26 08:59 concurrent run of two builds of Waterfox Current 2019.10 as a single task.zip
• https://put.re/player/kEEDx9dy.mp4

Side note: if other users of Linux can not reproduce this concurrency with build 20191015121210 alongside build 20191023104314, it might be due to #1200 (comment) where I chose to pollute an installation of 20191015121210 with an omni.ja that was apparently from a Windows installation. Slap me!

Reproducible with fresh installations of 20191015121210 and 20191023104314.

[grahamperrin]

As far as I can tell there's no risk to user data – profiles are separate – so (exotically) this may be viewed as a feature, not a bug.

More specifically:

1. concurrent running – the subject of this issue – may be viewed as a feature
2. two profiles for a single version of the application may be viewed as a bug.

I'm inclined to close this issue and raise a new issue for (2), however it's difficult for me to be certain about the origin(s) of the separation between profiles. I mean,

Reproducible with fresh installations of 20191015121210 and 20191023104314.

– whilst the applications were fresh, the profile environments were not.

Resolution of part A of the following issue might lead to a surer test routine:

• Waterfox Current first run UX · Issue #1142 · MrAlex94/Waterfox