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

"Can't execute code from a freed script" error when testing Sencha ExtJS applications in IE11 #2639

Closed
kot-lex opened this issue Jul 17, 2018 · 10 comments
Assignees
Labels
AREA: client STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: hammerhead TYPE: bug The described behavior is considered as wrong (bug).
Milestone

Comments

@kot-lex
Copy link

kot-lex commented Jul 17, 2018

Are you requesting a feature or reporting a bug?

Bug

What is the current behavior?

Test of ExtJS application in IE11 fails with "Can't execute code from a freed script"

What is the expected behavior?

Test passes as it does in all other browsers

How would you reproduce the current behavior (if this is a bug)?

Clone repo with example https://github.com/kot-lex/testcafe-test
run npm install
run npm run test

Provide the test code and the tested page URL (if applicable)

Repo with sample test https://github.com/kot-lex/testcafe-test

Tested page URL:
http://examples.sencha.com/extjs/6.6.0/examples/admin-dashboard/

Test code

test('My first test', async t => {
    const button = Selector('.x-treelist-item-text').withExactText('Email');
    await t
        .click(button)
    });

Specify your

  • operating system: Windows 10
  • testcafe version: 0.20.4
  • node.js version: 8.11.3
@AndreyBelym AndreyBelym added TYPE: bug The described behavior is considered as wrong (bug). SYSTEM: hammerhead AREA: client labels Jul 18, 2018
@AndreyBelym AndreyBelym added this to the Planned milestone Jul 18, 2018
@AndreyBelym
Copy link
Contributor

Hi @kot-lex, I've reproduced the issue. We need some time to investigate what's going wrong on the page.

@kot-lex
Copy link
Author

kot-lex commented Jul 25, 2018

Hi @AndreyBelym, any update on this?

@kot-lex
Copy link
Author

kot-lex commented Aug 2, 2018

Any news? Ability to run test in Internet Explorer 11 is critical for us.

@AndreyBelym
Copy link
Contributor

Hi @kot-lex, unfortunately page's code is very complex, and we don't have any significant results.

@kot-lex
Copy link
Author

kot-lex commented Aug 7, 2018

@AndreyBelym is there any chance of this issue being resolved by your team anytime soon?
If there is anything we can do on our side to help you address the issue please let me know.

@Farfurix
Copy link
Contributor

I'm working on it.

@miherlosev
Copy link
Collaborator

Fixed in #2779

@AndreyBelym
Copy link
Contributor

Hi @kot-lex! The fix is released in [email protected], you can install it with npm i testcafe@latest and try it on your machine.

@kot-lex
Copy link
Author

kot-lex commented Sep 4, 2018

Works like a charm, thank you guys!

@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs or feature requests. For TestCafe API, usage and configuration inquiries, we recommend asking them on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
AREA: client STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: hammerhead TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

5 participants