In a Discourse support thread titled ‘Ember jquery Out of Memory when typing response,’ dschaper reports that typing in the reply box on Discourse 2.7.0beta4 causes browser lockups with ‘Out of Memory’ errors in Ember-jquery. Despite disabling features, clearing CDN caches, and bootstrapping a new container, the issue persisted. Server logs showed ‘worker_connections not enough’ alerts, possibly due to CDN cache purges. Johani suggested testing in safe-mode, which initially failed with an ‘Oops’ page, but later worked dschaper. riking questioned whether the issue was client- or server-side and requested screenshots and logs. dschaper shared screenshots and a backtrace pointing to the ‘discourse-feature-voting’ plugin. Eventually, dschaper identified the culprit as a theme component, ‘discourse-abbrify-words,’ which, when removed, resolved the issue. codinghorror suggested switching to Discourse’s hosted service, but dschaper noted that self-hosting remains cost-effective given their current setup with Bunny.net, Backblaze B2, and DigitalOcean, though they acknowledge the need for a full infrastructure refresh due to legacy configuration.
Safe mode, all boxes checked gives me the Oops page:
Oops
The software powering this discussion forum encountered an unexpected problem. We apologize for the inconvenience.
Detailed information about the error was logged, and an automatic notification generated. We'll take a look at it.
No further action is necessary. However, if the error condition persists, you can provide additional detail, including steps to reproduce the error, by posting a discussion topic in the site's feedback category.
I’m slightly confused – this is pointing to a server problem, but the rest of your descriptions are about client side problems.
The safe-mode failure implies extra server side problems.
Can you take a screenshot of the “out of memory” error?
Try to visit /logs. Is there anything interesting there?
The error.log messages may be from me dumping the CDN cache and it doing a pull.
Everything was working great hours earlier. I bootstrapped a new image when the beta was released, I had bootstrapped an image to pull in the fixes for the S3 CDN avatar flair fixes from Falco.
I’ve just bootstrapped a new image and put it up.
When you type a single char in the reply box it freezes up.
We’ve considered it but I don’t think the costs for hosted are offset by the costs of self-hosting and self-supporting.
The number of pageviews per month and the number of admin/mods we have would put us in the “Ask for a Quote” category, versus what we pay now for Bunny.net (CDN), Backblaze B2 and the no-cost (after credits) from DO for the droplet. Discourse really isn’t painful to maintain, it’s just been neglected for a long time as it was set up by someone that’s not part of the team anymore and there was no real explanation of why and what was done. Probably due for a complete redo of the whole setup now that we have things in buckets.