Some jobs on CI are failing with error code 134
This means that JVM crashed, here is what we can read in logs about this crash:

#

1. A fatal error has been detected by the Java Runtime Environment:
   #
2. SIGSEGV (0xb) at pc=0x0062c453, pid=19100, tid=3074149280
   #
3. JRE version: 6.0_30-b12
4. Java VM: Java HotSpot(TM) Server VM (20.5-b03 mixed mode linux-x86 )
5. Problematic frame:
6. C [libc.so.6+0x6b453] unsigned long+0x23
   #
7. An error report file with more information is saved as:
8. /qa/hudson_ws/workspace/jbosstools-3.3_trunk.component--freemarker/sources/tests/org.jboss.ide.eclipse.freemarker.test/hs_err_pid19100.log
   #
9. If you would like to submit a bug report, please visit:
10. http://java.sun.com/webapps/bugreport/crash.jsp
11. The crash happened outside the Java Virtual Machine in native code.
12. See problematic frame for where to report the bug.
    #

Affected jobs:

• http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--central/507/console
• https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--freemarker/951/console

This does not seem deterministic as for freemarker, the exactly same job