-
-
Notifications
You must be signed in to change notification settings - Fork 239
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
HttpListener exceptions will occur when more than 6 simultaneous accesses #42
Comments
I wonder if I am having the same issue. No errors in the application, but if more than a small number of simultaneous connections to the server are made the refresh rate slows down to nothing. it starts at 500ms and gradually degenerate to a refresh every minute or more. how do the listener exceptions manifest? |
I checked 8 viewer for like 5 minutes without any issues , can you check the latest version v1.2
|
There are no errors in the application, but if more than a small number of simultaneous connections are made to the server, the update rate is reduced to nothing. We are trying to connect more than 8 devices at the same time and even if we reconnect the quality, the server does not work, and even stops working completely. Could you help us? |
@Yerikajc can you please specify the app version and the specs for the device running ScreenTask (CPU & RAM) ? also the used configuration for the app so that we can try to replicate your conditions. |
@ElBedeawi the version we are using is 1.2 the latest version. The CPU that the devices have are Intel® Core™ i5-1145G7 11th generation (4 cores, 8 MB cache, up to 4.4 GHz, 15 W), with 8 GB DDR4 RAM.
|
@EslaMx7 don't we have a newer version that supports WebRTC, Can we provide it here to Yerikajc may be it will give him a better performance. |
@ElBedeawi @EslaMx7 If you could provide it, I would appreciate it. |
memory leak fixed in this release, might improve things: https://github.com/mchampanis/ScreenTask/releases/tag/1.3 |
No description provided.
The text was updated successfully, but these errors were encountered: