Crash in racob-x64.dll on Windows
Description
Attachments
2
- 14 Apr 2014, 03:24 PM
- 18 Dec 2013, 03:23 PM
Gliffy Diagrams
Activity
Show:
Cris April 15, 2014 at 9:58 AM
The same issue here:
Ferdinand Holzer April 14, 2014 at 3:26 PMEdited
I suspect that this is somehow related to the windows event log input. It's the only input in use in our config.
edit: we don't run the web in the same jvm, so i doubt that it's related to that
Details
Details
Assignee
Logstash Developers
Logstash DevelopersReporter
Tom Robinson
Tom RobinsonLabels
Affects versions
Created December 18, 2013 at 3:23 PM
Updated April 15, 2014 at 9:58 AM
Running using:
java -jar logstash-1.3.1-flatjar.jar agent -f logstash.conf – web
#
A fatal error has been detected by the Java Runtime Environment:
#
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffc410f1aa4, pid=6560, tid=28164
#
JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode windows-amd64 compressed oops)
Problematic frame:
C [racob-x64.dll+0x1aa4]
#
Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
An error report file with more information is saved as:
C:\Users\TRobinson\Downloads\logstash\hs_err_pid6560.log
#
If you would like to submit a bug report, please visit:
http://bugreport.sun.com/bugreport/crash.jsp
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.
#