odoo/odoo#193332
Created by fw-bot
Statuses:
- legal/cla: Contributor License Agreement check
- ci/runbot: Odoo Test Suite
- ci/upgrade_enterprise: Test upgrades for enterprise master
- ci/template: Contact runbot team on discord for help.
- ci/style: Optional style check. Ignore it only if strictly necessary.
- ci/security: Required security check. Can only be ignored by security team.
- label
- odoo-dev:saas-18.1-18.0-mem-leak-aab-lHbX-fw
- head
- a95902b7b461d89b5fbc45195270ed4d3f3f4b38
- merged
- 10 months ago by JavaScript, Mathieu Duckerts-Antoine (dam)
| odoo/odoo | |
|---|---|
| 18.0 | #193283 |
| saas-18.1 | #193332 |
| saas-18.2 | |
| saas-18.3 | |
| saas-18.4 | |
| 19.0 | |
| master | #193334 |
[FW][FIX] web: hoot: correctly garbage collect between suites
Since [1], we force the garbage collector to run between each hoot test suite. However, since chrome 124, this no longer seemed to produce the desirable effect. Indeed, memory graphs of the test suites were no longer predictable. The garbage collector seemed to work differently from a build to another, even with the same code.
This is probably due to this change [2] in chrome, coming with version 124. Hopefully, the commit message gave us a hint on a way to fix our issue.
[1] a3ef39dae4a7cd6c96f14958744ac8d8bd2064c9
[2] https://chromium.googlesource.com/chromium/src/+/ae7269f134ede59c815b22c1fd042b26bab96b7a
Description of the issue/feature this PR addresses:
Current behavior before PR:
Desired behavior after PR is merged:
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: #193283