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
constWebSocket=require('ws');consturl=`ws://localhost:3000/echo`;console.log(`Connecting to URL: ${url}`);asyncfunctionrun(){constws=newWebSocket(url);ws.on('message',functionincoming(data){console.log(data.toString());});ws.on('pong',functionheartbeat(){ws.isAlive=true;});ws.on('error',functionerror(err){console.error(err);});ws.on('close',functionclose(){console.log('connection closed');});// send a message every 5mssetInterval(()=>{ws.send('Hello!');},5);}run();
When the nodejs script receives a SIGINT the following occurs:
$ python -m socketify main:app
Listening on port 3000
[1] 9977 segmentation fault python -m socketify main:app
Expected behavior
socketify should not have segfaulted
Desktop (please complete the following information):
I ran this on Ventura MacOS 13.5 (22G74), using python 3.11.5 and node 18.16.0
The text was updated successfully, but these errors were encountered:
Describe the bug
Segmentation faults occur during the following scenario:
Segfaults only occur when awaiting an async function in the socketify websocket message function.
Note: I also get segfaults before the connections are closed when sending high volumes of messages from 2 connections.
To Reproduce
simple example of socketify websocket server
When the nodejs script receives a SIGINT the following occurs:
Expected behavior
socketify should not have segfaulted
Desktop (please complete the following information):
I ran this on Ventura MacOS 13.5 (22G74), using python 3.11.5 and node 18.16.0
The text was updated successfully, but these errors were encountered: