You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have used whoops for some months in a project where I built a custom error handler that integrates nicely with whoops.
Recently I noticed that when an exception gets thrown after a relativly "large" stack trace (maybe 100 frames in whoops ) the error page initially rendors correctly bit as soon as I click one different frame in the side panel my entire browser freezes and then crashes. Tried in chrome and firefox on two pcs.
Is this to be expected? I could not find anything in the docs regarding setting a frame limit.
Thank you,
Calvin
The text was updated successfully, but these errors were encountered:
I suppose a setting to show only the top x frames could make sense to work around any limitations in the browser. A PR is welcome.
denis-sokolov
changed the title
[Question] Stack trace crashes chrome and firefox
Limit the number of frames shown to prevent browser crashes
Aug 6, 2021
Hello,
I have used whoops for some months in a project where I built a custom error handler that integrates nicely with whoops.
Recently I noticed that when an exception gets thrown after a relativly "large" stack trace (maybe 100 frames in whoops ) the error page initially rendors correctly bit as soon as I click one different frame in the side panel my entire browser freezes and then crashes. Tried in chrome and firefox on two pcs.
Is this to be expected? I could not find anything in the docs regarding setting a frame limit.
Thank you,
Calvin
The text was updated successfully, but these errors were encountered: