Thanks for tracking this down Rob! You nailed down the problem before it even had a chance to cause too much disruption for users. \o/
I'll help lobby to get the patch merged.
Steve, I'm interested to hear if you still notice problems. If so, we'll stay on it until we get a resolution.
It's interesting how many things we're uncovering about the Java-JRuby integration. I only wish we'd get a bit more input from that team for how much of a workout it's getting here.
-Dan
sebersole,
Thank you for your reply. Have you tried with the following steps? If not can you please try?
First make sure you are using the Gradle daemon. You can enable the Gradle daemon if you have the following defined in a file named gradle.properties in the root of your build (or in ~/.gradle/gradle.properties):
org.gradle.daemon=true
You should then be able to reproduce the crash consistently after after X times of running the build. For my very simple build it took about 15 tries, but this will vary depending on how many classes are being loaded by Gradle's ClassLoader.
I'm confident that I solved a leak for my particular build. This would certainly fix at least "a leak" for anyone using asciidoctor gradle plugin. However, I cannot be certain that it was the only leak and thus I cannot be certain it will resolve your issue completely.
Cheers,
Rob
If you reply to this email, your message will be added to the discussion below:http://discuss.asciidoctor.org/Gradle-plugin-and-permgen-tp1040p1092.htmlTo start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML
| Free forum by Nabble | Edit this page |