Skip to content

Only one Lumaview instance should be allowed to run at one time #559

@ericweiner

Description

@ericweiner

I have now seen at multiple places a confusing log where I can't be certain about what is going on. Ports are being occupied, but it isn't clear if this is a hardware problem, or perhaps a zombie instance is still running (tying up the ports) OR maybe someone double clicked on it too quickly and run it twice.

We need to have a check that is run at the very beginning of LVP startup that checks to see if LVP is already running, and to NOT run (ideally putting up a message saying there is already another instance running.).

I don't know the best way of doing this (i.e. check for a running process? Setting a flag? Something that happens immediately once the program is started so that a fast double click gets blocked.) , but IMO this needs to get into the next release.

Assigning everyone, not sure who the best is to implement. If you take it on, please unassign the others.

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions