I left that tab open for a few hours and when I came back my laptop was really hot and the CPU fans kicked in.
You must log in or # to comment.
this will probably be fixed in v0.18 since they’re disabling websockets
How is a websocket being the problem in this?
it’s how they’re doing live updates on pages, they’re disabling the auto updates
Ah, disabling auto updates. So it was just server issue then. Websockets are normally just fine. It shouldn’t cause any cpu issues when implemented properly.
when implemented properly
it’s probably a buggy implementation which is why they’re disabling it for now, and yea it causes server load too
Fair. Bit of a shame though. I always enjoy leaving the comment page open and follow the new comments live as they get posted.
eh I don’t really like it cause it messes up your scroll position if you were reading something, easy enough to just manually refresh and sort by new
I wouldn’t be surprised if they later fix it and bring it back as an option
When I’m on at home, the page I’m on constantly refreshes. That means it is making calls to the server frequently. There may be a way to turn it off and only update page when you make a refresh request, but I’m not that savvy yet
yea v0.18 turns off the constant refreshes
It seems to use more over time
I’ve had a similar issue. I think it’s tied to how posts seemingly endlessly rain in. Probably will be fixed in the next update, but I’m not sure when exactly that will happen.
Firefox and Lemmy tabs left open to the front page for hours are not currently a good mix.
deleted by creator
Depending on the operating system or performance counter the utilisation is displayed per core. So an 8 core (or thread, with hyperthreading) CPU will show a max utilisation of 800%.
deleted by creator
