SingleFile fails to complete page capture for Washington Post articles with NS_ERROR_OUT_OF_MEMORY

[jobel30263]

Issue Description

SingleFile consistently fails to complete the page capture process for Washington Post articles, interrupting at Step 3 of 3 with the following error:

Exception... "Out of Memory" nsresult: "0x8007000e (NS_ERROR_OUT_OF_MEMORY)" location: "JS frame :: sandbox eval code..."

This issue is specific to Washington Post webpages and occurs across multiple browsers, including Firefox 136.01, Brave 134.0.6998.89, Edge 134.0.3124.72, and Opera 117.0.540

Additional Details

• The error occurs consistently for all Washington Post articles.
• Other websites do not exhibit this issue when using SingleFile.
• The problem persists across different browser platforms, suggesting it's not browser-specific.
• This is a new problem starting March, 2025; earlier, there was no problem with these webpages.

Possible Causes

1. Recent changes in Washington Post's webpage structure or content delivery.
2. Interaction between SingleFile's rendering process and Washington Post's webpage elements.
3. Potential memory management issues within SingleFile when processing Washington Post content.

Request for Assistance

1. Is there a known workaround to successfully capture Washington Post articles using SingleFile?
2. Can the SingleFile team investigate potential memory optimization for processing Washington Post content?
3. Are there any configuration changes (or work-arounds) that users can make to mitigate this issue?

Additional Information

Please let me know if you need any further details or specific examples of Washington Post URLs that trigger this error. I'm happy to provide any additional information that may assist in resolving this issue. Thanks.