15
Codazed
6y

Me: Runs app

*Crash with error*

Me: Changes one thing, then runs again

*Crash with different error in another part of code*

Me: Fixes that error and runs again

*A FATAL ERROR HAS BEEN DETECTED BY THE JAVA RUNTIME ENVIRONMENT*

Me: Runs app again, "Maybe it was just a hiccup."

*A FATAL ERROR HAS BEEN DETECTED BY THE JAVA RUNTIME ENVIRONMENT*

Me: Chucks laptop out window. Goes to gaming PC to play Dark Souls 3, because it's less angering than this.

Comments
  • 12
    I see the problem, you are using java
  • 2
    I’ve started writing down what error I get and what steps I took to solve it just to try to cut down on the madness in the future. If I’m going to struggle to figure out why I get a random unhelpful error message, I might as well document how I fixed it so I don’t have to live with the additional frustration of knowing I’ve come across the error before and don’t remember what I did.
  • 1
    @mundo03 I like Java... most of the time. I hate it when stupid crap like this happens.
  • 2
    Shits bad when DS3 is more chill than what you're currently doing.
  • 1
  • 0
    Flush all caches and make sure you are running it with a correct jvm. Karaf, liferay and lots of other tools tend to coredump at boot-time when run with too new jvm version or non-ora jvm.

    Either that or you have a faulty dimm. Happened to me once
  • 0
    Java OOM can be annouying... give it more memory, and try again.
Add Comment