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

Exception in building JMeter(Execution failed for task ':src:dist:runGui'.) #6261

Closed
ibingdian opened this issue Mar 29, 2024 · 3 comments

Comments

@ibingdian
Copy link

ibingdian commented Mar 29, 2024

Steps to reproduce the problem

the jmeter source get by git,the jmeter version is lastest.

./gradlew.bat runGui is fail.

Getting Build Failed with exception while building using ./gradlew.bat runGui:

PS D:\xxx\jmeter> ./gradlew.bat runGui
Type-safe project accessors is an incubating feature.

Configure project :
Building JMeter 6.0.0-SNAPSHOT

Configure project :src:components
RenderInBrowser is excluded from compilation. If you want to compile it, add -PenableJavaFx

Configure project :src:dist-check
Certain tests will be skipped as they depend on external services and fail too often. Please add -PenableFlaky to enable them: [batchHttp4ImplDigestAuth, batchHttp4ImplPreemptiveBasicAuthJava, batchHttp4ImplPreemptiveBasicAuth, batc
hSlowCharsFeatureHttpClient4, batchSlowCharsFeatureJava, batchTCP_TESTS, batchTestKeepAlive, batchTestRedirectionPolicies, batchJDBC_TESTS, batchResponseDecompression]

Task :src:dist:runGui
WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
================================================================================
Don't use GUI mode for load testing !, only for Test creation and Test debugging.
For load testing, use CLI Mode (was NON GUI):
jmeter -n -t [jmx file] -l [results file] -e -o [Path to web report folder]
& increase Java Heap to meet your test requirements:
Modify current env variable HEAP="-Xms1g -Xmx1g -XX:MaxMetaspaceSize=256m" in the jmeter batch file
Check : https://jmeter.apache.org/usermanual/best-practices.html
================================================================================
An unrecoverable stack overflow has occurred.

A fatal error has been detected by the Java Runtime Environment:

EXCEPTION_STACK_OVERFLOW (0xc00000fd) at pc=0x00007ff89b91c5b7, pid=17424, tid=15452

JRE version: Java(TM) SE Runtime Environment (17.0.10+11) (build 17.0.10+11-LTS-240)
Java VM: Java HotSpot(TM) 64-Bit Server VM (17.0.10+11-LTS-240, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
Problematic frame:
C [awt.dll+0xec5b7]

No core dump will be written. Minidumps are not enabled by default on client versions of Windows

An error report file with more information is saved as:
D:\2024\source\jmeter\bin\hs_err_pid17424.log

If you would like to submit a bug report, please visit:
https://bugreport.java.com/bugreport/crash.jsp
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.

Task :src:dist:runGui FAILED
checksum-dependency elapsed time: 2340ms, configurations processed: 69 (add -PchecksumTimingsPrint to print detailed timings)
checksum-dependency elapsed time: 2623ms, configurations processed: 219 (add -PchecksumTimingsPrint to print detailed timings)

FAILURE: Build failed with an exception.

  • What went wrong:
    Execution failed for task ':src:dist:runGui'.

Process 'command 'D:\ly\sw\jdk-17.0.10\bin\java.exe'' finished with non-zero exit value 1

  • Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Get more help at https://help.gradle.org.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.5/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD FAILED in 13s
161 actionable tasks: 18 executed, 143 up-to-date

JMeter Version

JMeter 6.0.0-SNAPSHOT

Java Version

17

kotlin Version

1.9.20

gradle Version

8.5

OS Version

windows

@vlsi
Copy link
Collaborator

vlsi commented Mar 29, 2024

Please check out the contents of hs_err_pid17424.log to see the reason for the failure.

@vlsi vlsi closed this as completed Mar 29, 2024
@ibingdian
Copy link
Author

ibingdian commented Mar 29, 2024

it is EXCEPTION_STACK_OVERFLOW in hs_err_pid17424.log.
how to fix the problem? i modify DEFAULT_JVM_OPTS in gradlew.bat ,but it not work.

hs_err_pid17424.log

@vlsi vlsi reopened this Apr 1, 2024
@ibingdian
Copy link
Author

this issue is repeatedly put in #6262,

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants