Skip to content

Option to open popouts in their own process #1291

@ari-cp

Description

@ari-cp

Problem
Right now, popout windows execute in the main window's process. This is fine for smaller applications, but data-intensive applications will run into memory issues fairly quickly. For example, consider a trading app with ticking tables and charts. A user might like to have 10-15 windows open at a time, all with ticking data. If all the socket handling, message processing and UI rendering is done in the main window, that process can get overloaded pretty quickly.

Framework
All

Proposed solution
I haven't dug into the weeds too much, but I gather this probably wouldn't be a simple feature to add. Has anyone else encountered any performance issues along the lines of what I described? Are there any known workarounds?

Alternatives considered
I am considering using dockview for all layout besides popouts and instead write my own window management implementation.

Additional context
Any other context, screenshots, or links to related issues/discussions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions