为提高效率，提问时请提供以下信息，问题描述清晰可优先响应。
【DM版本】:[{“版本信息”:“DM Database Server 64 V8\n”},{“版本信息”:“DB Version: 0x7000c”}]
【操作系统】：NeoKylin Linux Desktop release 7.0 (aarch64)
【CPU】:aarch64
【问题描述】*：之前可以正常执行./manager。从昨天开始，执行./manager会报异常，日志是：
[root@localhost tool]# ./manager

(Manager:5312): GLib-GObject-WARNING **: 14:05:11.472: invalid (NULL) pointer instance

(Manager:5312): GLib-GObject-CRITICAL **: 14:05:11.473: g_signal_connect_data: assertion ‘G_TYPE_CHECK_INSTANCE (instance)’ failed

(Manager:5312): Gtk-CRITICAL **: 14:05:11.474: IA__gtk_settings_get_for_screen: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:5312): Gtk-WARNING **: 14:05:11.508: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window

(Manager:5312): Gtk-WARNING **: 14:05:11.508: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window

(Manager:5312): Gdk-CRITICAL **: 14:05:11.509: IA__gdk_screen_get_display: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:5312): Gdk-CRITICAL **: 14:05:11.509: IA__gdk_display_get_pointer: assertion ‘GDK_IS_DISPLAY (display)’ failed

(Manager:5312): Gtk-WARNING **: 14:05:11.509: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window

(Manager:5312): Gdk-CRITICAL **: 14:05:11.509: IA__gdk_screen_get_n_monitors: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:5312): Gtk-WARNING **: 14:05:11.509: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window

(Manager:5312): Gdk-CRITICAL **: 14:05:11.509: IA__gdk_screen_get_monitor_geometry: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:5312): Gdk-CRITICAL **: 14:05:11.509: IA__gdk_screen_get_default_colormap: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:5312): Gdk-CRITICAL **: 14:05:11.509: IA__gdk_colormap_get_visual: assertion ‘GDK_IS_COLORMAP (colormap)’ failed

(Manager:5312): Gdk-CRITICAL **: 14:05:11.509: IA__gdk_screen_get_default_colormap: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:5312): Gdk-CRITICAL **: 14:05:11.509: IA__gdk_screen_get_root_window: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:5312): Gdk-CRITICAL **: 14:05:11.509: IA__gdk_screen_get_root_window: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:5312): Gdk-CRITICAL **: 14:05:11.510: IA__gdk_window_new: assertion ‘GDK_IS_WINDOW (parent)’ failed

A fatal error has been detected by the Java Runtime Environment:

SIGSEGV (0xb) at pc=0x0000ffff999d5ff0, pid=5312, tid=0x0000ffffb144c200

JRE version: OpenJDK Runtime Environment (8.0_151-b12) (build 1.8.0_151-8u151-b12-0kord0.16.04.2k1-b12)

Java VM: OpenJDK 64-Bit Server VM (25.151-b12 mixed mode linux-aarch64 compressed oops)

Problematic frame:

C [libgdk-x11-2.0.so.0+0x7bff0] gdk_window_enable_synchronized_configure+0x10

Failed to write core dump. Core dumps have been disabled. To enable core dumping, try “ulimit -c unlimited” before starting Java again

An error report file with more information is saved as:

/dm8/tool/hs_err_pid5312.log

The crash happened outside the Java Virtual Machine in native code.

See problematic frame for where to report the bug.

./manager: 行 20: 5312 已放弃 “$JAVA_HOME/bin/java” -Xms256m -Xmx2048m -XX:+PerfDisableSharedMem -DDM_HOME=“$DM_HOME” -Djava.library.path=“$DM_HOME/bin” -Ddameng.log.file=“$TOOL_HOME/log4j.xml” -DeclipseHome=“$TOOL_HOME” -Dosgi.nl=“$INSTALL_LANGUAGE” -Ddameng.dts.explorer.root=“$TOOL_HOME/workspace/local/dts” -Ddameng.isql.explorer.root=“$TOOL_HOME/workspace/local/isql” -Duse_bak2=true -Dapp.name=manager -jar “$TOOL_HOME/plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar” -os linux -ws gtk -arch x86_64 -showsplash “$TOOL_HOME/manager.bmp” -data “$TOOL_HOME/workspace/manager” -product com.dameng.manager.product -name Manager
[root@localhost tool]#

请问是什么原因？感谢……