-
-
Notifications
You must be signed in to change notification settings - Fork 311
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
Portmaster Network Activity gets stuck on "Loading Chart" and doesn't show any network activity #1595
Comments
Hey @netExtra, thank you for raising this issue with us. After a first review we noticed that we will require the Debug Info for further investigation. However, you haven't supplied any Debug Info in your report. Please collect Debug Info from Portmaster while the reported issue is present. |
The same error scenario on my laptop (running Windows 11) |
+1 on a Windows 11 Laptop |
I reported that issue a few months back. But now I wonder if I really had the issue or if I just didn't scroll down enough lol because nothing has changed but the issue is no longer there. |
This issue has been automatically marked as inactive because it has not had activity in the past two months. If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics. |
This issue has been automatically closed because it has not had recent activity. Thank you for your contributions. If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord. |
Windows 10
What happened:
Install application. Select Network Activity
What did you expect to happen?:
Network Activity Chart appears but it doesn't. Instead stuck on "Loading Chart". Screenshot attached
How did you reproduce it?:
Works on initial install, but after a short time stops working. Even restarting doesn't work. Only way to fix is to reinstall the application.
Logs attached
-->
2024-06-24-17-36-47.error.log
2024-06-24-17-36-47.log
2024-06-24-15-27-26.log
The text was updated successfully, but these errors were encountered: