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
Describe the bug
Same issue as #514, Fatal error in V8: v8_ArrayBuffer_NewBackingStore
According to the issue #514 and PR #532, fatal error when using Electron v21+ should be fixed. But I still bump into the same issue when using Electron v23.3.2 and ZeroMQ v5.3.1.
I am using ZeroMQ with zerorpc-node, but I forked zerorpc-node because it's outdated. And change its dependency to zeromq@5.3.1
After some debugging, I found the app crashed at zeromq/lib/index.js:655.
varmessage=this._zmq.readv();// can throw
Could anyone please tell me some idea to solve this problem? Thanks
Reproducing
Client written in JavaScript (tested ok on Node.js but crashed on Electron)
[21036:0321/132855.727:ERROR:node_bindings.cc(146)] Fatal error in V8: v8_ArrayBuffer_NewBackingStore When the V8 Sandbox is enabled, ArrayBuffer backing stores must be allocated inside the sandbox address space. Please use an appropriate ArrayBuffer::Allocator to allocate these buffers. [21036:0321/132855.727:ERROR:crashpad_client_win.cc(844)] not connected
My code crashes on the first socket.send(); that appears.
Describe the bug
Same issue as #514, Fatal error in V8: v8_ArrayBuffer_NewBackingStore
According to the issue #514 and PR #532, fatal error when using Electron v21+ should be fixed. But I still bump into the same issue when using Electron v23.3.2 and ZeroMQ v5.3.1.
I am using ZeroMQ with zerorpc-node, but I forked zerorpc-node because it's outdated. And change its dependency to zeromq@5.3.1
After some debugging, I found the app crashed at zeromq/lib/index.js:655.
Could anyone please tell me some idea to solve this problem? Thanks
Reproducing
Client written in JavaScript (tested ok on Node.js but crashed on Electron)
Server written in Python 3.10:
Expected behavior
No more crash and receive response from the server.
Tested on
The text was updated successfully, but these errors were encountered: