Hi,
Today, several JVM processes crashed due to an assertion failure. All processes were up for about 200 days.
The log states:
java: DB.h:103: R* DBTable<R>::getRecord(jint, bool) [with R = TelemetryExtRecord]: Assertion `index >= 0' failed.
Environment:
[YourKit Java Profiler 9.0.9] (options disablestacktelemetry,disableexceptiontelemetry,builtinprobes=none)
java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.9) (6b20-1.9.9-0ubuntu1~10.04.2)
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
As far as I can see no telemetry was active at the moment of the crash.
Before I start updating the profiler version, is this a known issue?
Regards,
Niels Beekman
JVM Crash (Assertion failed)
-
- Posts: 6172
- Joined: Wed Aug 11, 2004 8:37 am
Re: JVM Crash (Assertion failed)
Hi Niels
Version 9.0.9 is unsupported for years. Please use the latest version 2013 instead:
http://www.yourkit.com/download
Best regards
Anton
Version 9.0.9 is unsupported for years. Please use the latest version 2013 instead:
http://www.yourkit.com/download
Best regards
Anton
-
- Posts: 19
- Joined: Tue Oct 23, 2007 12:42 pm
Re: JVM Crash (Assertion failed)
Anton,
Yes, I know. But my question is still: will updating the agent help? I.e. is this a bug that has been fixed.
--Niels
Yes, I know. But my question is still: will updating the agent help? I.e. is this a bug that has been fixed.
--Niels
-
- Posts: 6172
- Joined: Wed Aug 11, 2004 8:37 am
Re: JVM Crash (Assertion failed)
As far as I remember, this bug was fixed. Anyway, it is always recommended to use the latest version because it contains all bug fixes and improvements.