wxMaxima help page causes PM to hang

[Stargate38]

Please always mention the name/domain of the website in question in your topic title.

Please try to include any relevant output from the Toolkit Error Console or the Developer Tools Web Console using the following procedure:

1) Clear any current output
2) Navigate or refresh the page in question
3) Copy and paste Errors or seemingly relevant Warnings into a single [ code ] block.

Code: Select all

**PASTE CONSOLE OUTPUT HERE**
I can't. The browser hangs almost immediately after hitting F1 in wxMaxima, so I can't get the Developer Tools to come up.

Page in question: https://maxima.sourceforge.io/docs/manu ... epage.html
It works fine in Edge (no hang, but uses a lot of RAM), but when I try to load it in PM, I get an immediate hang, and even after waiting a while, it still refuses to respond. Any chance of a fix?

[Night Wing]

The page in question does more than just hang for me. It totally freezes and locks up and stays that way. In order to get my linux Pale Moon back, I had to use my Taskmanager to terminate something named PID 12632 (whatever that means) which I did. Then I was able to reboot Pale Moon.

[Gemmaugr]

For me it loads for a long time, then stops responding for a bit, goes back to loading, then locks up the browser.

If I try to press F12 at the start, it just stops responding immediately.

[andyprough]

This page loads for me on Basilisk after a several minute hang. It is an extremely long page with a lot of links.

I got the following errors in the Error Console, but they appear to be secondary font, uBlock messaging, hash and certificate errors which are not the likely cause of the hang:

Code: Select all

Timestamp: 07/20/2026 10:28:17 PM Error: downloadable font: Size of decompressed WOFF 2.0 is less than compressed size (font-family: "DejaVu Sans" style:normal weight:normal stretch:normal src index:0) source: (invalid URI) 
Timestamp: 07/20/2026 10:28:17 PM Error: downloadable font: rejected by sanitizer (font-family: "DejaVu Sans" style:normal weight:normal stretch:normal src index:0) source: (invalid URI) 
Timestamp: 07/20/2026 10:28:17 PM Error: downloadable font: font load failed (font-family: "DejaVu Sans" style:normal weight:normal stretch:normal src index:0) source: (invalid URI) 
Timestamp: 07/20/2026 10:28:17 PM Warning: Security wrapper denied access to property "setTimeout" on privileged Javascript object. Support for exposing privileged objects to untrusted content via __exposedProps__ is being gradually removed - use WebIDL bindings or Components.utils.cloneInto instead. Note that only the first denied property access from a given global object will be reported. Source File: chrome://ublock0/content/js/contentscript.js Line: 428 
Timestamp: 07/20/2026 10:28:17 PM Error: TypeError: vAPI.setTimeout is not a function Source File: chrome://ublock0/content/js/contentscript.js Line: 428 
Timestamp: 07/20/2026 10:28:22 PM Error: None of the “sha384” hashes in the integrity attribute match the content of the subresource. Source File: https://maxima.sourceforge.io/docs/manual/maxima_singlepage.html Line: 0 
Timestamp: 07/20/2026 10:33:43 PM Error: Expected certificate attribute 'issuerName' value incorrect, expected: 'CN=DigiCert SHA2 Secure Server CA,O=DigiCert Inc,C=US', got: 'CN=R13,O=Let's Encrypt,C=US'. Source File: resource://gre/modules/CertUtils.jsm Line: 109 Timestamp: 07/20/2026 10:33:43 PM Error: Expected certificate attribute 'issuerName' value incorrect, expected: 'CN=thawte SSL CA - G2,O="thawte, Inc.",C=US', got: 'CN=R13,O=Let's Encrypt,C=US'. Source File: resource://gre/modules/CertUtils.jsm Line: 109 
Timestamp: 07/20/2026 10:33:43 PM Error: Certificate checks failed. See previous errors for details. Source File: resource://gre/modules/CertUtils.jsm Line: 112 Timestamp: 07/20/2026 10:33:43 PM Error: 1784604823794 Toolkit.GMP ERROR GMPInstallManager.onLoadXML could not load xml: [Exception... "Certificate checks failed. See previous errors for details." nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: resource://gre/modules/CertUtils.jsm :: validateCert :: line 113" data: no] Source File: resource://gre/modules/Log.jsm Line: 753 
Timestamp: 07/20/2026 10:33:43 PM Error: 1784604823794 Toolkit.GMP ERROR GMPInstallManager.simpleCheckAndInstall Could not check for addons: {"target":{},"status":200,"message":"[Exception... \"Certificate checks failed. See previous errors for details.\" nsresult: \"0x80070057 (NS_ERROR_ILLEGAL_VALUE)\" location: \"JS frame :: resource://gre/modules/CertUtils.jsm :: validateCert :: line 113\" data: no]"} Source File: resource://gre/modules/Log.jsm Line: 753

The main issue appears to be that maxima_singlepage.html is an extremely large single-page manual. The Maxima documentation page explicitly offers the reference manual in separate HTML, PDF, and single-page HTML forms, and the single-page version contains a very large table of contents with dozens of chapters and many subsections. This URL: https://maxima.sourceforge.io/docs/manu ... epage.html
is the “everything in one HTML document” version. That kind of page can be brutal for single-process browsers.

Edge loads it but uses a lot of RAM; Basilisk eventually loads it after several minutes; Pale Moon can lock up entirely. Opening DevTools/F12 makes it worse because the browser then has to inspect/index a huge DOM/source document.

A practical workaround is to avoid the single-page version and use the split HTML manual instead:
https://maxima.sourceforge.io/docs/manual/index.html

[Moonchild]

A critical note that this has nothing to do with being single process or not; it's brutal to any browser. It's only because of being a user-facing lockup instead of an internal one where it makes a practical difference.
There just isn't a reasonable way this document can be rendered without trying to lay out almost its entire content in memory. Its structure prevents the normal excessive performance inhibiting mitigations like partial load and segmented display from working.

[Kris_88]

The page is indeed large and takes a couple of minutes to load (during which time the browser freezes and unfreezes several times). Task Manager shows that the full load actually takes much longer than the first pages of the document begin to display. But overall, everything works fine.
And interestingly, in PM 34.1.0 (32-bit, windows), the document loads significantly faster than in 34.2.2.

Updated: Oh yeah, it turns out I'm not using the latest browser version. I tried 34.3.1, and it really does freeze for a long time without any visible progress. The processor is busy, but the memory doesn't increase. In older browser versions, the memory increases, and the page loads completely. I couldn't wait for the page to load in 34.3.1.

[adoxa]

It appears to be something with handling pre overflow; here's a userstyle to restore visible overflow.

Code: Select all

/* ==UserStyle==
@name         Maxima single-page manual
@namespace    adoxa
@version      1.0.0
@description  Restore visible overflow on pre.example elements to speed up loading.
@author       adoxa
==/UserStyle== */

@namespace url(http://www.w3.org/1999/xhtml);

@-moz-document url("https://maxima.sourceforge.io/docs/manual/maxima_singlepage.html") {
    pre.example {
        overflow: visible !important;
    }
}

[andyprough]

It appears to be something with handling pre overflow; here's a userstyle to restore visible overflow.

That userstyle worked for me with the Stylem extension on Pale Moon - the page opened, paused for several seconds, and then quickly finished loading fully. I'm able to scroll through the page without any interruption.