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

Webmediaplayer error when running tests #235

Open
jonathanbataire opened this issue May 30, 2023 · 3 comments
Open

Webmediaplayer error when running tests #235

jonathanbataire opened this issue May 30, 2023 · 3 comments

Comments

@jonathanbataire
Copy link

jonathanbataire commented May 30, 2023

Sometimes run into the following error when running thess tests. Seem to be a memory leak bug in chromium

  • harness v2.4.0
  • Can not replicate in v3.0.10
ConsoleMessage {
    _type: 'error',
    _text: 'Blocked attempt to create a WebMediaPlayer as there are too many WebMediaPlayers already in existence. See crbug.com/1144736#c27',
    _args: [],
    _stackTraceLocations: [ [Object] ]
  },

@jonathanbataire
Copy link
Author

jonathanbataire commented Jul 20, 2023

recently been working on this PR https://github.com/medic/config-ug-vht/pull/803 which introduces a geopoint widget in forms
this has made this issue more persistent. Found some solutions

problem:

Rapidly referencing harness object (like in a loop), while filling in forms with widgets, without restarting harness.

solution:

  • some tests were badly written not optimal. rewrote these for optimization.
  • group tests in nested describes where i can stop and start harness in the before and after hooks between problematic tests

@kennsippell
Copy link
Member

Hey @jonathanbataire . I think harness.clear() in between tests should be sufficient between tests. Hopefully you don't actually have to start/stop. Are you finding this to be the case?

@jonathanbataire
Copy link
Author

Hey @jonathanbataire . I think harness.clear() in between tests should be sufficient between tests. Hopefully you don't actually have to start/stop. Are you finding this to be the case?

wasnt enough i think, its always been in the beforeEach but would still fail
ended up splitting the problematic tests into separate test suites
about 2 files

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

2 participants