Crash when editing tFileOutputMSXML tree configuration

[Johan_jns]

Hello,

When editing the XML Tree of the component tFileOutputMSXML, after adding a few sub element to the rootTag Talend crash

Talend versions :
Talend Cloud Data Management Platform R2024-01 
TOS_DI-20211109_1610-V8.0.1

System : Linux 6.7.4-arch1-1

Crash log attached

Has anyone else encountered this?

[Xiaodi_Shi]

Hello,

We are not yet targeting Java 18.  What dependencies you have that requires JRE 18? 

Please refer to this online installation guide about:TalendHelpCenter:Compatible Java Environments.

The supported Java platforms are OpenJDK and Oracle JDK. The recommended distribution for OpenJDK is Zulu

17	Supported from R2023-10 onwards
11	Supported

Best regards

Sabrina

[Johan_jns]

Hello,

I was using for this test Oracle JDK 11
In the log : JRE version: Java(TM) SE Runtime Environment 18.9 (11.0.21+9) (build 11.0.21+9-LTS-193)

The 18.9 refers to the date it was released - 09/2018 and not Java 18.9 ( https://stackoverflow.com/questions/74825299/why-does-java-11-version-command-shows-java-18-x-as-out... )

[Xiaodi_Shi]

Hello,

Thanks for your confirmation for java version. It is very informative for us.

Could you please open the error log generated automatically by the Studio to see whether you have error stack trace there about this crash issue when editing tFileOutputMSXML tree configuration? If you do that, we will appreciate it a lot if you can paste it here.

About how to open this error log: in your Studio, click Window to open the menu, then select Show View->General->Error Log. Once you see an error, double click it.

Best regards

Sabrina

[Johan_jns]

Hello
A crash log hs_err_pid31499.log is attached on the first post, it was generated by talend when it crashed, would that work  ?

Best regards

Johan

[Johan_jns]

Here is the output of the Terminal on which i start Talend and the log corresponding to the crash.
I see only Information and Warn message on "View->General->Error Log" when i start Talend after the crash


../Talend-Studio-20231027_1100-V8.0.1 % ./Talend-Studio-linux-gtk-x86_64
SWT Webkit: Warning, You are using an old version of webkitgtk. (pre 2.4) BrowserFunction functionality will not be avaliable
SWT WebKit: error initializing DBus server, dBusServer == 0
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Warning: NLS unused message: Voir in: org.eclipse.ui.internal.editors.text.TextEditorMessages
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007b9cf272743b, pid=6099, tid=6100
#
# JRE version: Java(TM) SE Runtime Environment 18.9 (11.0.21+9) (build 11.0.21+9-LTS-193)
# Java VM: Java HotSpot(TM) 64-Bit Server VM 18.9 (11.0.21+9-LTS-193, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C [libgtk-3.so.0+0x32743b]
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /home/user/Talends/Talend-Studio-20231027_1100-V8.0.1/core.6099)
#
# An error report file with more information is saved as:
# /home/user/Talends/Talend-Studio-20231027_1100-V8.0.1/hs_err_pid6099.log
#
# If you would like to submit a bug report, please visit:
# https://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#


hs_err_pid6099.log is attached to this comment

[Xiaodi_Shi]

Hello,

Does it crash only when editing tFileOutputMSXML tree configuration or it reproduces via executing a job in your studio?

We met a similar issue before due to window OS update but it is not applicable for your use case as you are using Linux. Could you please try a new fresh installation of talend studio to see if it is working well?

Best regards

Sabrina

[Johan_jns]

Hello,

It only crashes when editing tFileOutputMSXML.

For now, our workaround is to create the component with the desired tree structure on an older version of Talend (6.5.1) and import it on Talend 8.0.1.

I have the problem on a brand new Talend Cloud Data Management Platform R2024-01.

2 of my colleagues, also on Linux, have the same problem.

Best regards

Johan