On a recently updated Fedora 38 I experience crashes when selecting a layout algorithm within the GUI
I have attached the used graphml File which I created using a recent yEd installation.
The graph comes originally from a TGF file
E.g. using Circular (OGDF) shows this behavior, but it is not only this one
Regards Andre
the command line output follows
~~~
$ ./Tulip-5.7.2.AppImage
Perspective running in standalone mode
QXcbConnection: XCB error: 3 (BadWindow), sequence: 1537, resource id: 10910629, major code: 40 (TranslateCoords), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 1632, resource id: 10911528, major code: 40 (TranslateCoords), minor code: 0
TLP_PLATEFORM linux
TLP_ARCH x86_64
TLP_COMPILER gcc
TLP_VERSION 5.7.2
TLP_STACK_BEGIN
00 0x00007fa39ba98840 in ogdf::CircularLayout::doCall(ogdf::GraphAttributes&, ogdf::ClusterStructure&) (+0xf0) from /tmp/.mount_Tulip-fXdtDD/usr/lib/tulip/libOGDFPlugins-5.7.2.so
01 0x00007fa39ba9d97b in ogdf::CircularLayout::call(ogdf::GraphAttributes&) (+0xb4b) from /tmp/.mount_Tulip-fXdtDD/usr/lib/tulip/libOGDFPlugins-5.7.2.so
02 0x00007fa39b9a963b in tlp::OGDFLayoutPluginBase::run() (+0x5b) from /tmp/.mount_Tulip-fXdtDD/usr/lib/tulip/libOGDFPlugins-5.7.2.so
03 0x00007fa3c337ed38 in tlp::Graph::applyAlgorithm(std::string const&, std::string&, tlp::DataSet, tlp::PluginProgress) (+0xa8) from /tmp/.mount_Tulip-fXdtDD/usr/bin/../lib64/libtulip-core-5.7.so
04 0x00007fa39890f111 in AlgorithmRunnerItem::run(tlp::Graph*) (+0xb71) from /tmp/.mount_Tulip-fXdtDD/usr/lib/tulip/perspective/libGraphPerspective-5.7.2.so
13 0x00007fa3c2479cc5 in QCoreApplication::notifyInternal2(QObject, QEvent) (+0x75) from /tmp/.mount_Tulip-fXdtDD/usr/bin/../lib64/libQt5Core.so.5
19 0x00007fa3c2479cc5 in QCoreApplication::notifyInternal2(QObject, QEvent) (+0x75) from /tmp/.mount_Tulip-fXdtDD/usr/bin/../lib64/libQt5Core.so.5
20 0x00007fa3c290146d in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) (+0x40d) from /tmp/.mount_Tulip-fXdtDD/usr/bin/../lib64/libQt5Gui.so.5
21 0x00007fa3c2903035 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) (+0x115) from /tmp/.mount_Tulip-fXdtDD/usr/bin/../lib64/libQt5Gui.so.5
22 0x00007fa3c28e005b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<qeventloop::processeventsflag>) (+0x7b) from /tmp/.mount_Tulip-fXdtDD/usr/bin/../lib64/libQt5Gui.so.5</qeventloop::processeventsflag>
24 0x00007fa3c11134fc in g_main_context_dispatch (+0x14c) from /lib64/libglib-2.0.so.0
25 0x00007fa3c11716b8 in ?? (+0xba6b8) from /lib64/libglib-2.0.so.0
26 0x00007fa3c1110b83 in g_main_context_iteration (+0x33) from /lib64/libglib-2.0.so.0
27 0x00007fa3c24cc24c in QEventDispatcherGlib::processEvents(QFlags<qeventloop::processeventsflag>) (+0x5c) from /tmp/.mount_Tulip-fXdtDD/usr/bin/../lib64/libQt5Core.so.5</qeventloop::processeventsflag>
28 0x00007fa3c2477f5b in QEventLoop::exec(QFlags<qeventloop::processeventsflag>) (+0xfb) from /tmp/.mount_Tulip-fXdtDD/usr/bin/../lib64/libQt5Core.so.5</qeventloop::processeventsflag>
29 0x00007fa3c2480834 in QCoreApplication::exec() (+0x84) from /tmp/.mount_Tulip-fXdtDD/usr/bin/../lib64/libQt5Core.so.5
30 0x000000000040ca03 in main (+0x9d3) from /tmp/.mount_Tulip-fXdtDD/usr/bin/tulip_perspective
31 0x00007fa3c1c49b8a in ?? (+0x27b8a) from /lib64/libc.so.6
32 0x00007fa3c1c49c4b in __libc_start_main (+0x8b) from /lib64/libc.so.6
TLP_STACK_END
I'm really sorry but I was unable to reproduce the crash you reported.
As I have no machine with your OS, I tried booting a virtual machine using Fedora-Workstation-Live-x86_64-38-1.6.iso,
then lauching Tulip-5.7.2.AppImage on your cairo.graphml file.
Every layout plugin I applied worked as expected.
Checked again, still crashes.
to make the AppImage extractable.
https://superuser.com/questions/1301583/how-can-i-extract-files-from-an-appimage
How exactly did you use this .iso file?
I installed virt-manager and started the systemd service.
Then i added the .iso to a new VM with 16Gb of RAM and 4 Cores, on my 32Gb i7-3770 host
Used the first option in the Grub menu (Live Image) with the .iso file.
Opened Firefox, downloaded from sourceforge the AppImage, chmodded it
and executed it and crash.
This all was very slow.
Regards Andre
Here is the output from the crash
Last edit: Andre Maute 2023-11-14
I did the same in using VirtualBox instead of virt-manager.
You can extract then run the appimage in doing this :
shouldn't it be possible to extract the contents of the AppImage
without running it? The documentation from AppImage suggests that this should be possible.
see
https://github.com/AppImage/AppImageKit
and search for
Could this be a CPU problem with my old Intel Core i7-3770 processor?
The combinations
with the AppImage don't crash
Hi Andre,
The issue likely comes to the fact that the OGDF library bundled in Tulip source folder is compiled with the following GCC flags:
-march=nativewhich produces binaries non portable across CPU architectures.Commenting lines 16 to 19 in file
tulip-5.7.2/thirdparty/OGDF/cmake/compiler-specifics.cmakeand rebuilding the AppImage should fix the issue.Cheers !
Indeed see Ticket #888, which we have already resolved, rebuilding from the source tar.gz doesn't show the crashes.
This makes sense, locally -march=native is always ok.
But for something portable like an AppImage, -march=native somehow works against the idea of portability.
Question: Would it be possible to drop that -march=native somehow for the AppImage?
Regards Andre
At least this behavior should be somehow documented.
Thanks to Antoine (the developer who integrated OGDF source in Tulip) for giving its 2 cents.
And thanks to you Andre for your recent reports.
So the AppImage build will be fixed for the next Tulip release.
Thany you all for your provided support
Andre