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

Stack overflow (Silverlight 5) #45

Open
DaveW-Enc opened this issue Feb 25, 2016 · 6 comments
Open

Stack overflow (Silverlight 5) #45

DaveW-Enc opened this issue Feb 25, 2016 · 6 comments

Comments

@DaveW-Enc
Copy link

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

@kerryjiang
Copy link
Owner

Sorry for my later response. Your stacktrace file is really useful.

I'll try to figure this issue out.

@kerryjiang
Copy link
Owner

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.

@kerryjiang
Copy link
Owner

Try this new constructor parameter receiveBufferSize.
cc97795

@DaveW-Enc
Copy link
Author

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 :)
stacktrace2.txt

@jpsfs
Copy link

jpsfs commented Feb 7, 2020

@DaveW-Enc / @kerryjiang Any update on this?
I'm facing the same issue and I've also increased the ReceivedBufferSize to double of the biggest message.

@DaveW-Enc
Copy link
Author

DaveW-Enc commented Feb 7, 2020 via email

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

3 participants