0
Under review

ws.furrynetwork.com is not available and is causing Javascript in browser to use all available CPU

Dekafox 12 months ago updated 12 months ago 2

On the upload page there is a script that keeps trying to load wss://ws.furrynetwork.com/ and failing. This happens both in Chrome and Firefox with no extensions. This causes the script to keep looping and use all available CPU.

I don't know if this is a temporary thing, but it is happening the morning of 7/14.

Under review

Hi there.

Could you share some more information with us? I wasn't able to replicate it.


Which page exactly are you on (as an url). Is there any security software on your computer, especially one that might be affecting websockets? 

It seems to be not doing it currently, or at least to the same extent.  It was happening on

https://furrynetwork.com/submissions/artwork/public/?page=1 or the draft one, and when you edit a submission from there.  As of right now, when I profiled it I did see several possibly related errors:

app.js:179 WebSocket connection to 'wss://ws.furrynetwork.com/' failed: Error in connection establishment: net::ERR_CERT_COMMON_NAME_INVALID

It isn't piling up and eating CPU currently like when I submitted this though.

As far as security software I'm just using Windows defender on Windows 10 so nothing out of the ordinary.