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

Dokka 0.9.13 crashes JVM on build. #135

Closed
ajalt opened this issue Jan 25, 2017 · 7 comments
Closed

Dokka 0.9.13 crashes JVM on build. #135

ajalt opened this issue Jan 25, 2017 · 7 comments

Comments

@ajalt
Copy link

ajalt commented Jan 25, 2017

I recently upgraded the Dokka version on an android library that I publish through jitpack.

It appears that Dokka is crashing the JVM when run on the Jitpack servers. I can not reproduce the crash on my local machine, but it happens on every build on jitpack.

Here's a log with a stacktrace and a thread dump that contains the error:
https://jitpack.io/com/github/jitpack-io/flexadapter/e9d8686/build.log

And here's another log with just a stacktrace, but that uses the gradle daemon:
https://jitpack.io/com/github/ajalt/flexadapter/140483df580a998b301d32ac3a37a67b793967a0/build.log

Here are my gradle files:
https://github.com/ajalt/flexadapter/blob/master/build.gradle
https://github.com/ajalt/flexadapter/blob/master/flexadapter/build.gradle

Let me know if there's any more information I can provide.

@semoro
Copy link
Contributor

semoro commented Jan 25, 2017

I noticed such crashes while development of new Dokka build configuration, I will check for workaround and answer soon.

@semoro
Copy link
Contributor

semoro commented Jan 25, 2017

It happens when you loading dokka plugin with working directory != directory with gradlew

@gurunars
Copy link

@ajalt sorry, which JDK do you happen to have locally? I, unfortunately, fully reproduce the issue. Is it a Sun one? Or OpenJDK?

@ajalt
Copy link
Author

ajalt commented Feb 27, 2017

From the log that I posted:

# JRE version: Java(TM) SE Runtime Environment (8.0_101-b13) (build 1.8.0_101-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.101-b13 mixed mode linux-amd64 compressed oops)

vm_info: Java HotSpot(TM) 64-Bit Server VM (25.101-b13) for linux-amd64 JRE (1.8.0_101-b13), built on Jun 22 2016 02:59:44 by "java_re" with gcc 4.3.0 20080428 (Red Hat 4.3.0-8)

Is that what you were looking for?

@gurunars
Copy link

@ajalt

openjdk version "1.8.0_76-release"
OpenJDK Runtime Environment (build 1.8.0_76-release-b03)
OpenJDK 64-Bit Server VM (build 25.76-b03, mixed mode)

Not the same, but close. The issue is reproducible locally.

@gurunars
Copy link

Tested on the latest Oracle JDK. Fails as well. Sdk version:

java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)

chibatching added a commit to chibatching/Kotpref that referenced this issue Mar 17, 2017
chibatching added a commit to chibatching/Kotpref that referenced this issue Mar 17, 2017
chibatching added a commit to chibatching/Kotpref that referenced this issue Mar 17, 2017
@semoro
Copy link
Contributor

semoro commented May 29, 2017

Fixed in 0.9.14

@semoro semoro closed this as completed May 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants