Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
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]
-
Testcase included:yes
-
Number of attachments :
Description
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 =>
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.
#