-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Getting out of memory error while running test in parallel #3205
Comments
@bachhavdipak Have you looked at a heap dump? |
@marcphilipp seeing how this issue involves a webdriver and parallel execution I reckon this is a variant of the problems solved by #3044. The difference being that this is using the I didn't know the right solution at the time but adding a @bachhavdipak can you still reproduce this problem on Java 11 or higher with a
If the problem persists with these settings on Java 11 and higher you will also have to file a bug report with Serenity at https://github.com/serenity-bdd/serenity-core. |
This is a followup of junit-team#3044 for the `dynamic` strategy. Fixes: junit-team#3205
I am not using Java9 as company policies not allowing
…On Fri, Mar 24, 2023 at 11:41 AM M.P. Korstanje ***@***.***> wrote:
@marcphilipp <https://github.com/marcphilipp> seeing how this issue
involves a webdriver and parallel execution I reckon this is a variant of
the problems solved by #3044
<#3044>. The difference being
that this is using the dynamic strategy instead of the fixed variant.
I didn't know the right solution at the time but adding a
junit.jupiter.execution.parallel.config.dynamic.max-pool-size-factor
property to limit the maximum pool size could solve this.
@bachhavdipak <https://github.com/bachhavdipak> can you still reproduce
this problem on Java 11 or higher with a fixed strategy and use these
condig settings:
junit.jupiter.execution.parallel.enabled=true
junit.jupiter.execution.parallel.config.strategy=fixed
junit.jupiter.execution.parallel.config.fixed.parallelism=2
junit.jupiter.execution.parallel.config.fixed.max-pool-size=2
If the problem persists with these settings you will also have to file a
bug report with Serenity at https://github.com/serenity-bdd/serenity-core.
—
Reply to this email directly, view it on GitHub
<#3205 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASMJ2WUGITCEMWKMGQD5FNDW5WB7VANCNFSM6AAAAAAWGLL7YQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This is a followup of junit-team#3044 for the `dynamic` strategy. Fixes: junit-team#3205
If you would like us to be able to process this issue, please provide the requested information. If the information is not provided within the next 3 weeks, we will be unable to proceed and this issue will be closed. |
@bachhavdipak Have you tried the settings suggested by @mpkorstanje in #3205 (comment)? |
No ,I cant update jdk version due to company policies and still using jdk 8. |
@bachhavdipak From your stacktrace above it looked like you're already using JDK 11:
Was that from a local experiment? |
@marcphilipp : I am using java version "1.8.0_281" on my local and trying to execute test through azure pipeline and experitest cloud browser. |
@bachhavdipak Do you have an explanation for why the initial stack trace you shared was generated by JDK 11.0.18? |
Getting out of memory error while running test in parallel . I am using below configuration along with annotation**@execution(SAME_THREAD)** in the class.
Error log:
Context
The text was updated successfully, but these errors were encountered: