JVM crash

[stickman]

Just noticed this topic.. i bought a new computer. and i get this error randomly which closes my client:

http://pastebin.com/vCLkMHL5

# EXCEPTION_ACCESS_VIOLATION
# Problematic frame:
# V [jvm.dll+0xa5815]

[Granger]

Just noticed this topic.. i bought a new computer. and i get this error randomly which closes my client:

http://pastebin.com/vCLkMHL5

# EXCEPTION_ACCESS_VIOLATION
# Problematic frame:
# V [jvm.dll+0xa5815]

New computer? Do a memory test with memtest86+, in case this runs through 3 iterations without errors run Prime 95 in torture mode for some hours.
Segfault in JVM is unrelated to problems with Intel graphics.

[MagicManICT]

Split off to its own thread. Didn't apply to the thread it was in.

[jorb]

Will look at it.

[loftar]

From the error log, it looks like either a hardware/driver fault or a JVM bug, the latter being fairly unlikely. I notice from the log that it's from 32-bit Java, so if this is still a problem (or a problem for someone else), you may want to upgrade to 64-bit Java, just in case it perturbs the bug out of existence. If it doesn't help, I can probably only concur in Granger's suggestion.

[shubla]

Installing latest (java 8) 64 bit version should be one of promoted announcements.
In 2017 theres not that many people that are using 32-bit computer.

[MagicManICT]

Installing latest (java 8) 64 bit version should be one of promoted announcements.
In 2017 theres not that many people that are using 32-bit computer.

If only we could get the major browsers to just run 64-bit versions standard, we here at Haven & Hearth wouldn't have to worry about such an issue. Instead, Java.com detects browser version, sees "oh, 32-bit," and the snowball rolls downhill. Same can be said for mozilla's auto-detect and Google. If instead they were to detect OS version (if I recall correctly, sites can see that via HTTP, but maybe it gets obfuscated anymore), they'd get it right.

[borka]

Installing latest (java 8) 64 bit version should be one of promoted announcements.
In 2017 theres not that many people that are using 32-bit computer.

If only we could get the major browsers to just run 64-bit versions standard, we here at Haven & Hearth wouldn't have to worry about such an issue. Instead, Java.com detects browser version, sees "oh, 32-bit," and the snowball rolls downhill. Same can be said for mozilla's auto-detect and Google. If instead they were to detect OS version (if I recall correctly, sites can see that via HTTP, but maybe it gets obfuscated anymore), they'd get it right.

hence that's why there is since long
viewtopic.php?f=42&t=40331

this doesn't care about your browser and unless you're wanting default client it isn't wise to enable Java in browser anyways for security reasons... ( i still opt for having a jar for default client instead of that ugly jnlp)

btw.


https://ftp.mozilla.org/pub/firefox/rel ... -EME-free/

[MagicManICT]

My point is it's a failure in the overall "path of progress" as we have gotten more advanced machines, but the software running them is stuck in 2000.

[borka]

"path of progress" is Windows 10 ... and OsXxxx ...

The problem is more that certain OS devs don't manage to distinct between "I know nothing i just want to run xx" and "It's my machine and i determine what's going on - don't fucking hide and shatter everything" ... the path of progress with those is clear ... and finally ends in "be happy that you get drivers (etc) with windows update anyways" and "no you can't use custom drivers (etc.) anymore" and "only signed stuff from our App Store" ...

2020 finally my totally bye bye to that ... i'll be happy still being able to do stuff fully manually then ... and i won't care about the problems the supporters of certain OS will have anymore ... besides the big huge middle fingers of not paying game devs that don't use API alternatives aswell ...

it's been the Fricklers that brought us here not the Wipers and Tilers