diff options
| author | Marc R. Hoffmann <hoffmann@mountainminds.com> | 2017-05-05 21:06:34 +0200 |
|---|---|---|
| committer | Evgeny Mandrikov <Godin@users.noreply.github.com> | 2017-05-05 21:06:34 +0200 |
| commit | c24df15ef7c3cd0d65c1e61768b54294f18cf857 (patch) | |
| tree | c92610dec129bc1738f8344380784dd24bab6081 /org.jacoco.doc/docroot | |
| parent | a9732678a977e7e95909f5adb438f1248daf2965 (diff) | |
| download | jacoco-c24df15ef7c3cd0d65c1e61768b54294f18cf857.tar.gz | |
Explanations for possible StackOverflowErrors (#528)
Diffstat (limited to 'org.jacoco.doc/docroot')
| -rw-r--r-- | org.jacoco.doc/docroot/doc/faq.html | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/org.jacoco.doc/docroot/doc/faq.html b/org.jacoco.doc/docroot/doc/faq.html index 0efbce51..5c5275ab 100644 --- a/org.jacoco.doc/docroot/doc/faq.html +++ b/org.jacoco.doc/docroot/doc/faq.html @@ -149,6 +149,21 @@ classpath and accessible from by the instrumented classes. </p> +<h3>Why do I get a <code>StackOverflowError</code> during code coverage analysis?</h3> +<p> + There are two known reasons for this: +</p> +<ul> + <li>Misconfiguration: If you configure two JaCoCo agents of different releases + they will instrument each other and cause a endless recursion. Check the + effective java command line and avoid such configurations.</li> + <li>Heavy stack usage: JaCoCo instrumentation adds a small runtime overhead + by adding a local variable to each method. If your application is already + close to the maximum stack size this can eventually lead to an + <code>StackOverflowError</code>. Increase the maximum java stack size with + the <code>-Xss</code> JVM option.</li> +</ul> + </div> <div class="footer"> <span class="right"><a href="@jacoco.home.url@">JaCoCo</a> @qualified.bundle.version@</span> |