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

[wasm] System.Runtime.InteropServices.JavaScript.JSException: Invalid JS object handle '17' #54152

Closed
pavelsavara opened this issue Jun 14, 2021 · 2 comments · Fixed by #55075
Assignees
Milestone

Comments

@pavelsavara
Copy link
Member

pavelsavara commented Jun 14, 2021

In unit test System.Net.WebSockets.Client.Tests.ConnectTest.ConnectAsync_CancellationRequestedAfterConnect_ThrowsOperationCanceledException on Browser on windows, with remote loopback in xharness.

Unhandled Exception:
System.Runtime.InteropServices.JavaScript.JSException: Invalid JS object handle '17'
    at System.Runtime.InteropServices.JavaScript.JSObject.GetObjectProperty(String name) in C:\\Dev\\runtime\\src\\libraries\\System.Private.Runtime.InteropServices.JavaScript\\src\\System\\Runtime\\InteropServices\\JavaScript\\JSObject.cs:line 105
    at System.Net.WebSockets.BrowserWebSocket.CloseAsyncCore(WebSocketCloseStatus closeStatus, String statusDescription, CancellationToken cancellationToken) in C:\\Dev\\runtime\\src\\libraries\\System.Net.WebSockets.Client\\src\\System\\Net\\WebSockets\\BrowserWebSockets\\BrowserWebSocket.cs:line 577
--- End of stack trace from previous location ---
    at System.Net.WebSockets.BrowserWebSocket.AbortRequest() in C:\\Dev\\runtime\\src\\libraries\\System.Net.WebSockets.Client\\src\\System\\Net\\WebSockets\\BrowserWebSockets\\BrowserWebSocket.cs:line 377
@pavelsavara pavelsavara added arch-wasm WebAssembly architecture area-System.Net.Http labels Jun 14, 2021
@pavelsavara pavelsavara self-assigned this Jun 14, 2021
@ghost
Copy link

ghost commented Jun 14, 2021

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

In unit test System.Net.WebSockets.Client.Tests.CloseTest.CloseAsync_CancelableEvenWhenPendingReceive_Throws on Browser on windows, with remote loopback in xharness.

Unhandled Exception:
System.Runtime.InteropServices.JavaScript.JSException: Invalid JS object handle '17'
    at System.Runtime.InteropServices.JavaScript.JSObject.GetObjectProperty(String name) in C:\\Dev\\runtime\\src\\libraries\\System.Private.Runtime.InteropServices.JavaScript\\src\\System\\Runtime\\InteropServices\\JavaScript\\JSObject.cs:line 105
    at System.Net.WebSockets.BrowserWebSocket.CloseAsyncCore(WebSocketCloseStatus closeStatus, String statusDescription, CancellationToken cancellationToken) in C:\\Dev\\runtime\\src\\libraries\\System.Net.WebSockets.Client\\src\\System\\Net\\WebSockets\\BrowserWebSockets\\BrowserWebSocket.cs:line 577
--- End of stack trace from previous location ---
    at System.Net.WebSockets.BrowserWebSocket.AbortRequest() in C:\\Dev\\runtime\\src\\libraries\\System.Net.WebSockets.Client\\src\\System\\Net\\WebSockets\\BrowserWebSockets\\BrowserWebSocket.cs:line 377
Author: pavelsavara
Assignees: pavelsavara
Labels:

arch-wasm, area-System.Net.Http

Milestone: -

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Jun 14, 2021
@marek-safar marek-safar added this to the 6.0.0 milestone Jun 16, 2021
@marek-safar marek-safar added area-System.Runtime.InteropServices.JavaScript and removed untriaged New issue has not been triaged by the area owner area-System.Net.Http labels Jun 16, 2021
@pavelsavara
Copy link
Member Author

  Unhandled Exception:
  System.Runtime.InteropServices.JavaScript.JSException: Invalid JS object handle '1'
     at System.Runtime.InteropServices.JavaScript.JSObject.GetObjectProperty(String name)
     at System.Net.WebSockets.BrowserWebSocket.CloseAsyncCore(WebSocketCloseStatus closeStatus, String statusDescription, CancellationToken cancellationToken)
  --- End of stack trace from previous location ---
     at System.Net.WebSockets.BrowserWebSocket.AbortRequest()
     at System.Threading.Tasks.Task.\u003C>c.\u003CThrowAsync>b__140_1(Object state)
     at System.Threading.QueueUserWorkItemCallbackDefaultContext.Execute()
     at System.Threading.ThreadPoolWorkQueue.Dispatch()
     at System.Threading.ThreadPool.Callback()
  ThreadPool Callback threw an unhandled exception of type System.Runtime.InteropServices.JavaScript.JSException

@pavelsavara pavelsavara changed the title [wasm][websocket] System.Runtime.InteropServices.JavaScript.JSException: Invalid JS object handle '17' [wasm] System.Runtime.InteropServices.JavaScript.JSException: Invalid JS object handle '17' Jun 29, 2021
@ghost ghost added in-pr There is an active PR which will close this issue when it is merged and removed in-pr There is an active PR which will close this issue when it is merged labels Jul 1, 2021
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Jul 12, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Aug 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants