0

I am running selenium tests with maven from jenkins and after running for 5 hours suddenly the tests stop working and following error The forked VM terminated without saying properly goodbye. VM crash or System.exit called

possible solution is to

  • increase heap size using argline in maven however it is not supported since Java 8 another
  • stop and restart the tests after few hours using jenkins or maven

What is best way to solve this problem?

Jitendra Jogeshwar
  • 43
  • 5
  • avoid calling `System.exit` from the test suite that you are running. Have you ensured that none of your tests are returning or exiting unexpectedly?(maven doesn't interpret it) – Naman Jan 07 '17 at 06:36
  • Yes no tests are calling System.exit – Jitendra Jogeshwar Jan 07 '17 at 11:54
  • Most probably there is some memory leak in your tests, slowly eating up all the memory till JVM crashes with OOM and dumps core and memory content. Try checking if there is anything eating memory when it should not be (e.g jconsole can be great help, default tool in JDK). – skandigraun Jan 07 '17 at 18:31
  • Please see http://stackoverflow.com/a/33757854 – Krishnan Mahadevan Jan 08 '17 at 04:40
  • @skandigraun all this is running on jenkins is there way to access jconsole in jenkins environment? – Jitendra Jogeshwar Jan 09 '17 at 04:57

0 Answers0