My environment is Windows 2008 x64 (not R2) and Java SE runtime 1.6.0_24-b07 (bundled). I'm experiencing the exact same problem.

# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x01d58282, pid=4408, tid=5712
#
# JRE version: 6.0_24-b07
# Java VM: Java HotSpot(TM) Client VM (19.1-b02 mixed mode windows-x86 )
# Problematic frame:
# J  org.kohsuke.stapler.jelly.groovy.GroovyFacet$1.dispatch(Lorg/kohsuke/stapler/RequestImpl;Lorg/kohsuke/stapler/ResponseImpl;Ljava/lang/Object;)Z
#
# An error report file with more information is saved as:
# C:\Windows\system32\hs_err_pid4408.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp

Definitely a critical issue.

This is a bug in the Java VM and there's probably not much Jenkins can do about it.
To have the slightest chance to fix this on Jenkins side, we would need at least the content of the mentioned report file
(# An error report file with more information is saved as:

1. C:\Windows\system32\hs_err_pid4408.log)

Unfortunately, the JVM is lying – that file is never created.

Seems to be the same issue as JENKINS-16416

Found it. The actual path name is:

• C:\Windows\SysWOW64\hs_err_pid4408.log

Looks like the timestamper plugin is triggering the problem. I think tnaigeon's comment is better applied to this issue.

Thanks for the tip of the path Geoff, found my logs there also.

Since I disabled the timestamper plugin, we've not seen the problem. That, and the consistent mention of the same plugin in the JVM dumps, seems to indicate a flaw in the plugin.

We also have not seen the problem since disabling the Timestamper plugin.

Code changed in jenkins
User: StevenGBrown
Path:
src/main/java/hudson/plugins/timestamper/TimestamperConfig.java
src/main/resources/hudson/plugins/timestamper/TimestamperConfig/config.groovy
src/main/resources/hudson/plugins/timestamper/TimestamperConfig/config.jelly
src/main/resources/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory/usersettings.groovy
src/main/resources/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory/usersettings.jelly
src/test/java/hudson/plugins/timestamper/TimestamperConfigTest.java
http://jenkins-ci.org/commit/timestamper-plugin/86ae3272544f4f5b443f3ed5cf3aa965c315b12b
Log:
Workaround JENKINS-16528 by switching from Groovy views to Jelly views

–
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

The Timestamper plugin (1.5.3 or later) will no longer trigger this VM crash, because it uses Jelly views instead of Groovy views.

This VM crash may still occur during other usages of Groovy views, e.g. uninstalling the Active Directory plugin: hs_err_pid7064.log.

Seems to be fixed for the timestamper plugin

I am having the same issue when trying to install Jenkins 1.541 on my Windows XP. It's a brand new installation, found no timestamper plugin.