-
Notifications
You must be signed in to change notification settings - Fork 275
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
Stack overflow (Silverlight 5) #45
Comments
Sorry for my later response. Your stacktrace file is really useful. I'll try to figure this issue out. |
Yes, it is caused by the package is too big and the underlying crypto library cannot handle this situation very well. It could be relieved by increasing the receive buffer size, but WebSocket4Net doesn't support it for now. I'll add this feature pretty soon, but you still need wait a while if you want to get this enhancement through NuGet. |
Try this new constructor parameter receiveBufferSize. |
Hi Kerry, Thanks for looking into this. I tried the new constructor parameter and set the receiveBufferSize to larger than the largest data packet that we will be receiving. Unfortunately, I still get the stack overflow. Here is another stack trace, it probably won't tell you anything new, but you never know :) |
@DaveW-Enc / @kerryjiang Any update on this? |
I haven’t heard anything since sending the second stack trace.
We had to remove WebSocket4Net and go with a commercial product instead.
|
WebSocket4Net is great - and thanks for continuing to support Silverlight for those of us that are stuck with it!
So far everything is working great except for a fairly regular stack overflow. Seems to happen when receiving a stream of 10Kb packets from the server?
stacktrace.txt
The text was updated successfully, but these errors were encountered: