Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI becomes unresponsive after entering new different discovery range #11

Open
tyalie opened this issue Mar 11, 2024 · 3 comments
Open
Labels
enhancement New feature or request

Comments

@tyalie
Copy link

tyalie commented Mar 11, 2024

As the title states

@Chleba
Copy link
Owner

Chleba commented Mar 11, 2024

Hi,
This may happen when you have a small amount of cores thanks to green tokio threads. You may try to wait a moment. The process of scanning is still running and after a while, the UI becomes responsive again.
I will address this issue in the near future.

@Chleba Chleba added the enhancement New feature or request label Mar 12, 2024
@tyalie
Copy link
Author

tyalie commented Mar 16, 2024

Hm. I was actually on a 12 core machine :/

@Chleba
Copy link
Owner

Chleba commented Mar 16, 2024

Hi,
Did you wait a while and then the UI became responsive again ?
I am thinking about a solution and will try a few things to fix this issue, but I would like to know if it freezes completely on Your PC or if it just lag for a moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants