Resolving Stack Overflow Errors in Weblutions Products

This guide covers how to diagnose and resolve stack overflow errors when they occur within Weblutions products such as FaxStore or related systems.

Stack overflow errors are typically reported inconsistently across deployments - meaning some servers experience them while others do not. This usually indicates a combination of environment conditions and specific execution paths, rather than a universal platform issue.

Table of Contents

When This Issue is Typically Reported

Stack overflow errors are most commonly reported when:

• performing a specific action repeatedly (checkout, page load, API request, etc.)

• handling large datasets or deeply nested content

• using custom modifications or integrations

• running on servers with limited resources*

• after updating dependencies or product versions

These errors are often intermittent and may not affect all users or environments equally.

*The most common cause over FaxStore deployments tends to be limited resources on the server, or allocated to Node. To increase the RAM limit on Node view the Increasing Memory Allocation start command parameters.

Likely Contributing Factors

Within Weblutions deployments, stack overflow errors are usually linked to one or more of the following

Custom Modifications

Changes to core logic, templates, hooks, or extensions can introduce recursive or circular execution paths.

Third-Party Integrations

External APIs, plugins, or custom scripts may unintentionally trigger repeated calls or loops.

Large or Complex Data Structures

Examples include:

• deeply nested categories or pages

• large carts or payloads

• recursive processing of objects (e.g. page trees, configs)
  

Corrupted or Inconsistent Dependencies

Improperly installed or partially corrupted node_modules can cause unstable runtime behavior. The Reinstalling Node Modules guide can assist with a complete reinstall of the dependencies.

Server Resource Constraints

Lower-end or overloaded servers may expose issues more frequently:

• high CPU usage

• low available RAM

• multiple heavy processes running

• swap usage or throttling
  

Outdated Builds or Mismatched Environments

Running outdated Node.js versions or dependencies can lead to unexpected execution issues.

Initial Information to Collect

Before making changes, gather the following:

• exact error message (Maximum call stack size exceeded)

• full stack trace from the console

  • For Weblutions products, the console will provide most details, if escalating to Weblutions Support, a screenshot will be sufficient.

• the action that triggers the issue - if possible

• whether the issue is consistent or intermittent

  • Does the product function or remain online for some time before the error?

• recent changes (updates, plugins, edits)

• current server resource usage while the application is and is not running (RAM / CPU)

This information is critical for identifying whether the issue is logic-based or environment-related.

Recommended Troubleshooting Steps

Follow these steps in order. After each step, attempt to reproduce the error if able.

1. Restart the application and retry the action to rule out temporary instability.

2. Corrupted or mismatched dependencies can be a common cause. The Reinstalling Node Modules guide can assist with a complete reinstall of the dependencies.

3. Disable extensions. In many Weblutions products extensions can be installed. Temporarily uninstall the extensions to rule out any custom modifications. If the error doesn't continue, add extensions one by one to narrow down a potential cause.

4. Identify the trigger action. Narrowing down a specific action which causes this error can be a great step to find an issue with the application.

5. Check the servers resource usages. Assess the CPU and RAM resource usage while the application is running (if able) and without. If the resources are spiking with the application running, increase the servers resources.

6. Collect the amount of CPU cores, and amount of RAM for escalation

7. Escalate to Weblutions Support and provide the following:

   1. Domain of the application

   2. Amount of RAM and CPU cores

   3. The results of the above steps

   4. A screenshot of the error in the console

With this information if escalated Weblutions will be able to assess and assist in diagnosing the issue for resolution.