The header part of a frame cannot be read from the data source. When using in Unity
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
I have a websocket server Windows Form app using the github version here and a unity client using the asset store version.
Whenever I press play in unity it works perfectly but when I stop playing, then try play again, it gives me this:
Exception thrown: 'WebSocketSharp.WebSocketException' in websocket-sharp.dll
20/11/2015 5:23:21 PM|Fatal|WebSocket.processException:1017|WebSocketSharp.WebSocketException: The header part of a frame cannot be read from the data source.
at WebSocketSharp.WebSocketFrame.processHeader(Byte[] header) in C:\Work\Bugpunch\websocket-sharp\websocket-sharp\WebSocketFrame.cs:line 444
at WebSocketSharp.WebSocketFrame.<>c__DisplayClass75_0.b__0(Byte[] bytes) in C:\Work\Bugpunch\websocket-sharp\websocket-sharp\WebSocketFrame.cs:line 540
at WebSocketSharp.Ext.<>c__DisplayClass47_0.b__0(IAsyncResult ar) in C:\Work\Bugpunch\websocket-sharp\websocket-sharp\Ext.cs:line 629
20/11/2015 5:23:21 PM|Error|WebSocketBehavior.Start:345|This session has already been started.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Unity stop-and-play-again cycle, then start with WebSocketFrame.cs at lines 444 and 540, Ext.cs at line 629, and WebSocketBehavior.Start at line 345. Trace the session and frame-reading lifecycle to determine why the second run reaches these errors; done means the repeated play cycle no longer produces the reported exception or already-started session error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, unity
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100