win32ole seg fault if a thread once used for win32ole dies
----------------------------------------------------------
Key: JRUBY-5424
URL: http://jira.codehaus.org/browse/JRUBY-5424
Project: JRuby
Issue Type: Bug
Components: win32ole, Windows
Environment: jruby 1.6.0.RC1 (ruby 1.8.7 patchlevel 330) (2011-01-24
406556b) (Java HotSpot(TM) Client VM 1.6.0_18) [Windows 7-x86-java]
Reporter: Roger Pack
Assignee: Thomas E Enebo
This looked slightly different than the previous seg fault/blowups, but might
be related.
code:
$ cat jruby_bug.rb
require 'rubygems'
require 'ruby-wmi'
Thread.new {
p piddy = WMI::Win32_Process.find(:first, :conditions => {'Name' =>
'xxx.exe'})
raise
}
sleep 1
WMI::Win32_Process.find(:first, :conditions => {'Name' => 'xxx.exe'})
output: $ \dev\ruby\downloads\jruby\bin\jruby jruby_bug.rb
PROGID: WbemScripting.SWbemLocator
nil
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x64da18a1, pid=4400, tid=3700
#
# JRE version: 6.0_18-b07
# Java VM: Java HotSpot(TM) Client VM (16.0-b13 mixed mode, sharing windows-x86
)
# Problematic frame:
# C [racob-x86.dll+0x18a1]
#
# An error report file with more information is saved as:
# C:\dev\ruby\sensible-cinema\hs_err_pid4400.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
