You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We rely on the browser web socket to communicate with the inspector frontend and when the message that comes from the profiler is large enough, the browser web socket crashes.
As a solution to this problem we should remove the web socket dependency and use the integrated inspector communication method - register a native object that would send/receive all messages that comes or goes to the device.
The issue could be easily reproduced if you try to profile sample-Tasks
The text was updated successfully, but these errors were encountered:
We rely on the browser web socket to communicate with the inspector frontend and when the message that comes from the profiler is large enough, the browser web socket crashes.
As a solution to this problem we should remove the web socket dependency and use the integrated inspector communication method - register a native object that would send/receive all messages that comes or goes to the device.
The issue could be easily reproduced if you try to profile sample-Tasks
The text was updated successfully, but these errors were encountered: