@zerok hehe now you have noticed what throwing stereotypes means :)
Did you run into this problem yourself?
@saper Yes, I did.
@zerok it think a reason maybe a writable mapping of memory pages when loading a dynamic memory, but I am not sure
@saper that being said, you have to admit that the error message posted there by, I presume, the JVM or Gradle isn't really helpful :)
@zerok well nobody posted a stackttrace even.
@saper True :)
@zerok I think you could try to trace the process and find the offending call, something like mmap()
@zerok one issue similar to that one is related to libc compatibility:
https://github.com/gradle/gradle/issues/1493
but I think it was a locking issue mentioned here:
turning off ".gradle" altogether might help. (No idea how)
@saper Thanks :)
@saper Sure it was 🙂 Though, throwing around with stereotypes doesn't help either 😉