| #2336 – [A] TypeError: Cannot read properties of undefined (reading 'length') |
| #2319 – [A] Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues |
| #2299 – [A] RangeError: Invalid string length |
| #2207 – 100% CPU useage and 504 Gateway error when making new article |
| #2191 – [A] ReferenceError: res is not defined |
| #2099 – Restricted Article CSS Bug |
| #1853 – Can't delete categories anymore |
| #1697 – [A] TypeError: Cannot read properties of undefined (reading 'cache') |
| #1693 – [A] Error: WebSocket was closed before the connection was established |
| #1571 – [A] Error: Request failed with status code 404 |
| #1555 – Broken Counting |
| #1551 – [A] Error: Request failed with status code 404 |
| #999 – Site not working (Node.JS error) |
| #906 – Styling Changes |
| #694 – [A] TypeError: Cannot read properties of undefined (reading 'catId') |
| #663 – Search data function err |
100% CPU useage and 504 Gateway error when making new article
By WildFyr |
Details
Status: Open
Affects Version(s):
N/ALabels: None
Fix Version: None
Category: Back-end (Databasing, error reports)
Description
Please see this support article for original post.
Expected behaviour:
A new article should be created and the website code should not hang/cook the CPU of the server
Current behaviour:
Upon clicking create article the website will load until it times out, on the servers end the CPU usage climes all the way up until it has reached the max. It will stay like this until you stop FaxDocs. Eventually FaxDocs will crash, and CPU usage will stay at 100% until you manually stop the node process.
Steps to reproduce:
Create a new article on the latest version of FaxDocs, using Node version 20.5.1 and MDC version 9.8.0
Activity
By FAXES | We believe this is an issue with the markdown convert package we use. I'll get it updated tomorrow and we can see how it goes from there.
By FAXES | I've updated the markdown convert package for the most part to resolve this issue, we still have some further tests to do. However, you can do
npm install markdownconvert@latest to get the new version which fixes this issue.