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

maximum callstack size exceeded on some webpages #2938

Closed
Ghxst opened this issue Jul 20, 2023 · 5 comments
Closed

maximum callstack size exceeded on some webpages #2938

Ghxst opened this issue Jul 20, 2023 · 5 comments
Labels
FREQUENCY: level 1 STATE: Stale Outdated issues automatically closed by the Stale bot TYPE: bug

Comments

@Ghxst
Copy link

Ghxst commented Jul 20, 2023

What is your Scenario?

We're running into an issue with some webpages crashing due to a maximum callstack size exceeded error.

What is the Current behavior?

Hammerhead.js attempts to parse resources that cause an error that makes the page crash.

What is the Expected behavior?

No page crash is expected.

What is your public website URL? (or attach your complete example)

https://www.marriott.com/sign-in.mi

What is your TestCafe test code?

node node_modules/gulp/bin/gulp multi-window-http-playground

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

  1. node node_modules/gulp/bin/gulp multi-window-http-playground
  2. navigate to https://www.marriott.com/sign-in.mi
  3. check console

TestCafe version

n/a

Node.js version

v18.16.0

Command-line arguments

n/a

Browser name(s) and version(s)

Chrome 114

Platform(s) and version(s)

Windows, Linux Ubuntu

Other

No response

@miherlosev
Copy link
Contributor

Hi @Ghxst,

Thank you for the shared information. I've reproduced the issue.

For team:
image

@Ghxst
Copy link
Author

Ghxst commented Jul 21, 2023

Thanks for picking this up so quickly. I would love to know how your team goes about fixing these issues and what the root cause is. If you have any info that would be awesome.

@Aleksey28
Copy link
Collaborator

Hi @Ghxst,

We don't have any information yet. We will research this matter promptly and update this thread once we have news.

Copy link

This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.

@github-actions github-actions bot added the STATE: Stale Outdated issues automatically closed by the Stale bot label Mar 16, 2024
Copy link

We're closing this issue after a prolonged period of inactivity. If it still affects you, please add a comment to this issue with up-to-date information. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FREQUENCY: level 1 STATE: Stale Outdated issues automatically closed by the Stale bot TYPE: bug
Projects
None yet
Development

No branches or pull requests

3 participants