Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RangeError: Maximum call stack size exceeded #166

Open
adamgundry opened this issue Feb 28, 2023 · 4 comments
Open

RangeError: Maximum call stack size exceeded #166

adamgundry opened this issue Feb 28, 2023 · 4 comments

Comments

@adamgundry
Copy link
Contributor

When analysing a large eventlog (~425M) generated with -hi profiling, I'm seeing no Detailed table in Chrome 110.0.5481.77, and the console contains "RangeError: Maximum call stack size exceeded". Firefox 109.0.1 seems to load the table successfully though (all 1276 pages of it). I'm guessing this is an issue in the underlying table component?

Uncaught RangeError: Maximum call stack size exceeded
    at Function.oe [as find] (....eventlog.html:38:6281)
    at w.fn.init.find (....eventlog.html:38:24400)
    at HTMLTableElement.<anonymous> (....eventlog.html:59:3279)
    at Function.each (....eventlog.html:38:2573)
    at w.fn.init.each (....eventlog.html:38:1240)
    at o.fn.fancyTable (....eventlog.html:59:3122)
    at HTMLDocument.<anonymous> (....eventlog.html:3608:152286)
    at l (....eventlog.html:38:29375)
    at c (....eventlog.html:38:29677)

eventlog2html version: 0.9.2
GHC version: 9.4.4

@FinleyMcIlwaine
Copy link

FinleyMcIlwaine commented Apr 19, 2023

I am seeing the same thing on a 392MB eventlog generated with -hi profiling. Specifically, profiling Haddock on the Adga codebase.

Building Haddock with the "default" (from ghcup) GHC 9.4.4 and doing a profile results in no issues. Doing the profile with a Haddock built by an IPE-enabled (default+ipe hadrian flavour) GHC 9.4.4 results in this issue. Firefox does load it successfully.

eventlog2html version: 0.10.0

@jberryman
Copy link

I'm getting this too, confirm firefox works for me

@TeofilC
Copy link
Contributor

TeofilC commented Oct 5, 2023

It looks like this error is being generated by the fancyTable js code. Maybe we could replace fancyTable with a different implementation that doesn't have this issue. That's probably easier than trying to patch fancyTable

@jberryman
Copy link

Seems like a WONTFIX in fancyTable : myspace-nu/jquery.fancyTable#31 myspace-nu/jquery.fancyTable#46

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants