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

signalr core null exception problem #87

Closed
kopan opened this issue Feb 10, 2022 · 5 comments
Closed

signalr core null exception problem #87

kopan opened this issue Feb 10, 2022 · 5 comments

Comments

@kopan
Copy link

kopan commented Feb 10, 2022

hubconnection.cs

this.rwLock.Dispose();

need null check

@Benedicht
Copy link
Owner

With regular usage it shouldn't be a problem. How did you triggeren the exception there?

@kopan
Copy link
Author

kopan commented Feb 10, 2022

With regular usage it shouldn't be a problem. How did you triggeren the exception there?

It occurs when you repeatedly connect to a server with slow response, such as accessing a US server from Asia.

@Benedicht
Copy link
Owner

You mean by reusing the HubConnection instance?

@kopan
Copy link
Author

kopan commented Feb 10, 2022

No, I always use a new hub connection instance.

@Benedicht
Copy link
Owner

Hmm, that's interesting. Could you set the plugin's log level to verbose by adding the following line somewhere in your startup code:

BestHTTP.HTTPManager.Logger.Level = BestHTTP.Logger.Loglevels.All;

Replicate the exception and send over the (Editor)log to me (you can send it to my email address too: besthttp@gmail.com). You can read more about logging in the plugin here: https://benedicht.github.io/BestHTTP-Documentation/pages/best_http2/global_topics/Logging.html

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

No branches or pull requests

2 participants