Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

[resolved] TOS A fatal error has been detected by the Java Runtime Environment

Hi all,
I have an error when I open TOS (TOS_DI-r113626-V5.3.2) in windows 7.
Talend opens but shut done few second later. A message appears : "Java was started but returned exit code=1"...
And i have a log :
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000007fee9436890, pid=1160, tid=5928
#
# JRE version: Java(TM) SE Runtime Environment (7.0_67-b01) (build 1.7.0_67-b01)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.65-b04 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C  
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
#  
# The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report

To see the whole post, download it here
Labels (3)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

Hi guys,
For "Window Update" problem, this is a known issue. Please refer to jira issue: https://jira.talendforge.org/browse/TUP-2246.
So far, this problem is probably caused by Microsoft Windows Update. Please uninstall the KB2977629 patch to resolve this issue when this issue occur.
Our apologies for the inconvenience.

Best regards
Sabrina

 

View solution in original post

14 Replies
lequette
Contributor
Contributor

Same problem for me with TOS DI 5.5.1, last change was Windows update
I'd tried TOSDI 32 and 64bits, java7 32 and 64bits => always crash
Same after reinstall TOS and java
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000007feec856890, pid=5888, tid=5892
#
# JRE version: Java(TM) SE Runtime Environment (7.0_67-b01) (build 1.7.0_67-b01)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.65-b04 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C  
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
#  
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
---------------  T H R E A D  ---


To see the whole post, download it here
OriginalPost.pdf
lequette
Contributor
Contributor

I've also tried a new installation in a fresh virtual Win7 installation with same java version => works
Works also with an older jdk (1.7u65) => less but crash
Anonymous
Not applicable
Author

Hi Marie_FR,
Did you install oracle 64bit JDK into Win7 or only JRE?
Best regards
Sabrina
Elosi_SCR
Contributor II
Contributor II

Hello,
I had the same issue on Windows 8.1 64 bits and Talend Platform for Data Services, Version: 5.3.1
Build id: r104014, it will appeared after a Windows Update friday 11 september.
After I do a rollback of the update, Talend Studio work again.
Thanks Microsoft....
lequette
Contributor
Contributor

Same problem on another computer (W7, TOS DI 5.5.1, jdk 1.7.0_51)
Looks like a Windows Update conflict
-------------
edit : i'd remove last Windows and .NET updates
no more crash for now
we can found reports for the same crash for Zend Studio and other Eclipse based software
Anonymous
Not applicable
Author

hi all,
@talenddTeam :any sticky for that crashing Windows update.
I've heard 'similar sound' around me, following windows update this week-end.
which Talend & windows OS is affected ?
regards
laurent
Anonymous
Not applicable
Author

Hi xdshi,
I installed JDK and JRE 7.
I don't understand because today my talend works. Nothing change.
Anonymous
Not applicable
Author

Hi all, 
Sorry I haven't seen before but I had changes : a Windows update on my computer.
lequette
Contributor
Contributor

At home, the kb2977629 patch seems to be the cause of the crash
No more crash for now after uninstalling it
Hoping that the problem no longer occurs