Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • M MathJax
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 304
    • Issues 304
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 15
    • Merge requests 15
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MathJax
  • MathJax
  • Issues
  • #1401
Closed
Open
Issue created Feb 27, 2016 by Administrator@rootContributor

MathJax 2.5 and 2.6.1 intermitent errors when timing out

Created by: migf

MathJax 2.5 and 2.6.1 may fail, in an uncontrolled way, to render formulas when the connection speed is low and the timout delay for loading/verifying files is exceeded. I detected the following cases:

  1. formulas appear as "[Math Processing Error]", the Javascript console showing a "too much recursion" error and sometimes also "TypeError: MathJax.Extension.MathEvents is undefined"
  2. formulas appear as source in grey, and the "too much recursion" error is shown
  3. after clearing cache and cached web content, formulas appear as source in text normal colour, and no errors are shown.

I think that MathJax should fail gracefully when timing out instead of entering an infinite loop or giving spurious error messages that may confuse page authors and users. Would it be possible to correct this behaviour?

Best regards, Miguel Filgueiras

Assignee
Assign to
Time tracking