Board index FlightGear Support

Segfault in launcher?

All general support: help on flying, installation, hardware, getting online etc. There are lots of users and developers to help you out.
Forum rules
In order to help you, we need to know a lot of information. Make sure to include answers to at least the following questions in your initial post.

- what OS (Windows Xp/Vista, Mac etc.) are you running?
- what FlightGear version do you use?
- what graphics card do you have?
- does the problem occur with any aircraft, at any airport?
- where did you download your aircraft/scenery from?
- is there any output printed to the console (black window)?
- copy&paste your commandline (tick the "Show commandline box on the last page of FGRun or the "Others" section on the Mac launcher).

Please report any bugs not specific to an aircraft on the issue tracker.
To run FlightGear on old computers with bad OpenGL support, please take a look at this wiki article.

Note: If you did not get a reponse, even after 7 days, you may want to check out the FlightGear mailing lists to ask your question there.

Segfault in launcher?

Postby mifi » Sun Mar 18, 2018 6:09 pm

hi

The past few days I have noticed a Segmentation fault, that was not here before, as soon as I click the 'Fly' button in the launcher.

I am on Linux (Ubuntu 16.04.x) and compiled the latest 'next' release 2018.2.0 using a fresh download_and_compile.sh downloaded this morning.
Graphics cards differ, both nVidia and AMD cards on different PC's.
The segfault occurs at any aircraft at any location, for as far as I have tried.

I have a special directory for fgaddon that is properly set up in the launcher, but when I delete it, the segfault is still there.
Fgfs started without the launcher works fine.

Command:
Code: Select all
./run_fgfs.sh --launcher


Output during startup:
Code: Select all
FlightGear:  Version 2018.2.0
FlightGear:  Build Type Dev
Built with GNU C++ version 5.4
Jenkins number/ID 0:none
scenery path not found:Path "/home/mifi/Software/Sources/fgfs53/next/install/flightgear/fgdata/Scenery"
NavCache at:Path "/home/mifi/.fgfs/navdata_2018_2.cache"
NavCache read-only flags is:0
NavCache: no main cache rebuild required
init package root at:Path "/home/mifi/fgfs/launcherdata/Aircraft"
catalog at:Path "/home/mifi/fgfs/launcherdata/Aircraft/org.flightgear.official" failed version check: need version: 2018.2.0
disabling catalog:org.flightgear.official
qrc:///qml/Settings.qml:220:21: Type SettingLineEdit unavailable
qrc:///qml/SettingLineEdit.qml:1:1: module "QtQuick" version 2.7 is not installed
qrc:///qml/Environment.qml:156:21: Type SettingLineEdit unavailable
qrc:///qml/SettingLineEdit.qml:1:1: module "QtQuick" version 2.7 is not installed
scenery path not found:Path "/home/mifi/Software/Sources/fgfs53/next/install/flightgear/fgdata/Scenery"
reading groundnet data from Path "/home/mifi/fgfs/launcherdata/TerraSync/Airports/L/F/M/LFMN.groundnet.xml"
parsing groundnet XML took 0
can't find principal aircraft  "dhc3W"  for variant: "/home/mifi/Software/Sources/fgfs53/flightgear-fgaddon/Aircraft/dhc3/dhc3A-set.xml"
can't find principal aircraft  "dhc3W"  for variant: "/home/mifi/Software/Sources/fgfs53/flightgear-fgaddon/Aircraft/dhc3/dhc3F-set.xml"
can't find principal aircraft  "Rascal10-JSBsim"  for variant: "/home/mifi/Software/Sources/fgfs53/flightgear-fgaddon/Aircraft/Rascal/Rascal110-JSBSim-set.xml"
have orphan packages: will become inaccesible
   orphan package:org.flightgear.official.dc3
downloaded catalog http://fgfs.goneabitbursar.com/official/catalog.xml, but version required 2018.2.0
failed refresh of  "http://fgfs.goneabitbursar.com/official/catalog.xml" : 7

Segmentation fault (core dumped)


Has anyone else noticed something like this? I searched for segfaults on the forum, but nothing recent in the launcher came up.

mifi
mifi
 
Posts: 327
Joined: Mon Jul 23, 2007 4:24 pm
Location: NL
Version: git next
OS: Ubuntu 18.04.x Gnome

Re: Segfault in launcher?

Postby Thorsten » Sun Mar 18, 2018 6:47 pm

There've been a couple of launcher crashes observed during the last month (some by myself) - I don't know whether there's any relation, but I've forwarded the issue to the mailing list.
Thorsten
 
Posts: 12490
Joined: Mon Nov 02, 2009 9:33 am

Re: Segfault in launcher?

Postby mifi » Mon Mar 19, 2018 8:24 am

Thanks Thorsten.
mifi
Last edited by bugman on Mon Mar 19, 2018 9:22 am, edited 1 time in total.
Reason: Please do not quote the entire previous post.
mifi
 
Posts: 327
Joined: Mon Jul 23, 2007 4:24 pm
Location: NL
Version: git next
OS: Ubuntu 18.04.x Gnome

Re: Segfault in launcher?

Postby Ovazor » Mon Mar 19, 2018 3:51 pm

Hello,

The same issue appeared to me this weekend. This is the problem with the launcher, not the FG - the simulation works perfectly if started with the command line.

Not only does the launcher crash after hitting the "fly" button, but the environment and setting tabs do not work.

I think that the problem maybe due to incompatible qt version - in mifi's output there are error messages about no having the QtQuick version 2.7 installed. Mine gives the same error.

Does anybody know the Qt version required for QtQuick 2.7? All I could find was, that according to https://doc.qt.io/qt-5.10/qtquickcontrols2-index.html Qt 5.7 includes QtQuick 2.7. I am using OpenSuse Leap 42.3, and it ships with Qt 5.6...I tried to update the Qt but that broke KDE.
Flying the Dakota
Ovazor
 
Posts: 76
Joined: Wed Feb 12, 2014 7:53 am
Location: Finland
Callsign: OH-OVA
Version: 2020.4.0
OS: OpenSUSE LEap 15.2

Re: Segfault in launcher?

Postby mifi » Mon Mar 19, 2018 5:16 pm

I noticed a commit earlier today:

Code: Select all
new 4c2e52c  Standardise QtQuick version to 2.4
4c2e52c is described below
Commit:    4c2e52c2dce59f20410c9ff8607119394fb2cba1
Author:    James Turner
Committer: James Turner
AuthorDate:    Mon Mar 19 08:22:11 2018 +0000

Standardise QtQuick version to 2.4

Will fix an issue reported on the forum where a 2.7 dep crept it.


This suggests it has been fixed. However, I cannot confirm, because there is a compile time error in src/GUI/QmlAircraftInfo.cxx. That will be fixed shortly, no doubt. I will check again tomorrow, but our problem has probably been dealt with already.

mifi
mifi
 
Posts: 327
Joined: Mon Jul 23, 2007 4:24 pm
Location: NL
Version: git next
OS: Ubuntu 18.04.x Gnome

Re: Segfault in launcher?

Postby mifi » Tue Mar 20, 2018 9:35 am

Well, this morning the compile time error was solved, the launcher looks different but good, but it still segfaults when I click 'Fly'.
Also, changing between the different tabs in the launcher is very slow.

The console shows a couple of qml errors. I hope that helps:
Code: Select all
Custom restore state on SettingsDateTimePicker
qrc:///qml/Summary.qml:249: TypeError: Cannot call method 'descriptionForState' of null
qrc:///qml/Summary.qml:249: TypeError: Cannot call method 'descriptionForState' of null
qrc:///qml/Summary.qml:65:19: Unable to assign [undefined] to QUrl
qrc:///qml/Summary.qml:65:19: Unable to assign [undefined] to QUrl
qrc:///qml/Summary.qml:249: TypeError: Cannot call method 'descriptionForState' of null
have orphan packages: will become inaccesible
   orphan package:org.flightgear.official.dc3
downloaded catalog http://fgfs.goneabitbursar.com/official/catalog.xml, but version required 2018.2.0
failed refresh of  "http://fgfs.goneabitbursar.com/official/catalog.xml" : 7

qrc:///qml/Summary.qml:65:19: Unable to assign [undefined] to QUrl
qrc:///qml/Summary.qml:65:19: Unable to assign [undefined] to QUrl
MP enabled, doing refresh
Segmentation fault (core dumped)


mifi
mifi
 
Posts: 327
Joined: Mon Jul 23, 2007 4:24 pm
Location: NL
Version: git next
OS: Ubuntu 18.04.x Gnome

Re: Segfault in launcher?

Postby Ovazor » Tue Mar 20, 2018 3:30 pm

I can confirm. Now the environment and setting tabs work, but hitting the fly button causes the launcher to crash.

Code: Select all
FlightGear:  Version 2018.2.0
FlightGear:  Build Type Dev
Built with GNU C++ version 4.8
Jenkins number/ID 0:none
NavCache at:Path "/home/ova/.fgfs/navdata_2018_2.cache"
NavCache read-only flags is:0
NavCache: no main cache rebuild required
init package root at:Path "/home/ova/.fgfs/Aircraft"
libpng warning: iCCP: known incorrect sRGB profile
reading groundnet data from Path "/home/ova/.fgfs/TerraSync/Airports/G/C/R/GCRR.groundnet.xml"
parsing groundnet XML took 0
Custom restore state on SettingsDateTimePicker
libpng warning: iCCP: known incorrect sRGB profile
qrc:///qml/Summary.qml:249: TypeError: Cannot call method 'descriptionForState' of null
qrc:///qml/Summary.qml:249: TypeError: Cannot call method 'descriptionForState' of null
qrc:///qml/Summary.qml:249: TypeError: Cannot call method 'descriptionForState' of null
Error: caught signal 11:
  /lib64/libc.so.6 : ()+0x34fe0
  /usr/lib64/libQt5Widgets.so.5 : QWidget::~QWidget()+0x186
  /usr/lib64/libQt5Widgets.so.5 : QWidget::~QWidget()+0x9
  /usr/lib64/libQt5Qml.so.5 : QV4::QObjectWrapper::destroyObject(bool)+0x113
  /usr/lib64/libQt5Qml.so.5 : QV4::MemoryManager::sweep(bool)+0x140
  /usr/lib64/libQt5Qml.so.5 : QV4::MemoryManager::~MemoryManager()+0x37
  /usr/lib64/libQt5Qml.so.5 : QV4::ExecutionEngine::~ExecutionEngine()+0x86
  /usr/lib64/libQt5Qml.so.5 : QV8Engine::~QV8Engine()+0x145
  /usr/lib64/libQt5Qml.so.5 : QV8Engine::~QV8Engine()+0x9
  /usr/lib64/libQt5Qml.so.5 : QJSEngine::~QJSEngine()+0x21
  /usr/lib64/libQt5Qml.so.5 : QQmlEngine::~QQmlEngine()+0x12d
  /usr/lib64/libQt5Qml.so.5 : QQmlEngine::~QQmlEngine()+0x9
  /usr/lib64/libQt5Core.so.5 : QObjectPrivate::deleteChildren()+0x65
  /usr/lib64/libQt5Widgets.so.5 : QWidget::~QWidget()+0x36f
  /usr/lib64/libQt5QuickWidgets.so.5 : QQuickWidget::~QQuickWidget()+0x9
  /usr/lib64/libQt5Core.so.5 : QObjectPrivate::deleteChildren()+0x65
  /usr/lib64/libQt5Widgets.so.5 : QWidget::~QWidget()+0x36f
  /usr/lib64/libQt5Widgets.so.5 : QWidget::~QWidget()+0x9
  /usr/lib64/libQt5Core.so.5 : QObjectPrivate::deleteChildren()+0x65
  /usr/lib64/libQt5Widgets.so.5 : QWidget::~QWidget()+0x36f
  /usr/lib64/libQt5Widgets.so.5 : QStackedWidget::~QStackedWidget()+0x9
  /usr/lib64/libQt5Core.so.5 : QObjectPrivate::deleteChildren()+0x65
  /usr/lib64/libQt5Widgets.so.5 : QWidget::~QWidget()+0x36f
  /usr/lib64/libQt5Widgets.so.5 : QWidget::~QWidget()+0x9
  /usr/lib64/libQt5Core.so.5 : QObjectPrivate::deleteChildren()+0x65
  /usr/lib64/libQt5Widgets.so.5 : QWidget::~QWidget()+0x36f
  fgfs : LauncherMainWindow::~LauncherMainWindow()+0x96
  fgfs : flightgear::runLauncherDialog()+0x293
  fgfs : fgMainInit(int, char**)+0x63c
  fgfs : main()+0x217
  /lib64/libc.so.6 : __libc_start_main()+0xf5
  fgfs : _start()+0x29
./fgstart.sh: line 3:  5435 Aborted                 (core dumped) fgfs --fg-root=/usr/local/games/fgdata --launcher
Flying the Dakota
Ovazor
 
Posts: 76
Joined: Wed Feb 12, 2014 7:53 am
Location: Finland
Callsign: OH-OVA
Version: 2020.4.0
OS: OpenSUSE LEap 15.2

Re: Segfault in launcher?

Postby mifi » Tue Mar 20, 2018 7:18 pm

I saw this update:

Code: Select all
Commit:    1c78c65b19c2f2061477625489a626137eaba094
Author:    James Turner
Committer: James Turner
AuthorDate:    Tue Mar 20 16:32:31 2018 +0000

Popup an error box when QtQuick errors occur.


I immediately updated and fired up the launcher that still segfaults on 'Fly', without a popup, but I noticed this on the console:

Code: Select all
qrc:///qml/Summary.qml:249: TypeError: Cannot call method 'descriptionForState' of null
have orphan packages: will become inaccesible
   orphan package:org.flightgear.official.dc3
downloaded catalog http://fgfs.goneabitbursar.com/official/catalog.xml, but version required 2018.2.0
failed refresh of  "http://fgfs.goneabitbursar.com/official/catalog.xml" : 7

Segmentation fault (core dumped)


I think I am looking at a null pointer reference.

mifi
mifi
 
Posts: 327
Joined: Mon Jul 23, 2007 4:24 pm
Location: NL
Version: git next
OS: Ubuntu 18.04.x Gnome

Re: Segfault in launcher?

Postby wkitty42 » Tue Mar 20, 2018 9:21 pm

i don't know why i'm not seeing these problems, guys...

can you do us a favor, too, please? go to the user control panel and update your profile with your OS and such so that it shows up in the right hand pane like you can see on my posts... that way we don't always have to ask someone what their system specs are if we forget... thanks! :)

PS: you can click on my nick and see more info in my profile... especially the center area at the top in the System tag...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 9146
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: Segfault in launcher?

Postby mifi » Wed Mar 21, 2018 11:55 am

can you do us a favor, too, please? go to the user control panel and update your profile with your OS and such so that it shows up in the right hand pane like you can see on my posts... that way we don't always have to ask someone what their system specs are if we forget...


Done.
I did not see a setting to make the 'system' show up in the right column, but it is in my profile now.
Is there anything else you want me to do to help? I am not a developer, but I do want to help if I can.

I am currently compiling a freshly updated OSG to see if that makes any difference. If it does, I will post here.

For the record:

Code: Select all
OS: Ubuntu16.04.x
GPU: AMD Radeon RX550 (by Asus)
CPU: Intel Core i7
16GB RAM, 1TB HD
FG compiled with d&c script
Built as 64bit native binaries.
Running with latest TerraSync scenery, FGData and FGAddon.


mifi
mifi
 
Posts: 327
Joined: Mon Jul 23, 2007 4:24 pm
Location: NL
Version: git next
OS: Ubuntu 18.04.x Gnome

Re: Segfault in launcher?

Postby mifi » Wed Mar 21, 2018 12:13 pm

I made a stack backtrace with gdb directly after the segfault. This is from the core file that is dumped into 'install/flightgear/bin' against the fgfs that is living there as well.
I hope this helps.

#0 0x00007f392670355d in QWidget::~QWidget() ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#1 0x00007f39267038d9 in QWidget::~QWidget() ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#2 0x00007f39253ade18 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#3 0x00007f392534736b in QV4::MemoryManager::sweep(bool) ()
from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#4 0x00007f3925347fd8 in QV4::MemoryManager::~MemoryManager() ()
from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#5 0x00007f392532dc21 in QV4::ExecutionEngine::~ExecutionEngine() ()
from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6 0x00007f392546fd09 in QV8Engine::~QV8Engine() ()
from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7 0x00007f392546ff29 in QV8Engine::~QV8Engine() ()
from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8 0x00007f39252c1a91 in QJSEngine::~QJSEngine() ()
from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9 0x00007f39253d9ad5 in QQmlEngine::~QQmlEngine() ()
from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x00007f39253d9b99 in QQmlEngine::~QQmlEngine() ()
from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x00007f3924f7228b in QObjectPrivate::deleteChildren() ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
---Type <return> to continue, or q <return> to quit---
#12 0x00007f3926703708 in QWidget::~QWidget() ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f392a2ca5d9 in QQuickWidget::~QQuickWidget() ()
from /usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5
#14 0x00007f3924f7228b in QObjectPrivate::deleteChildren() ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f3926703708 in QWidget::~QWidget() ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007f39267038d9 in QWidget::~QWidget() ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x00007f3924f7228b in QObjectPrivate::deleteChildren() ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f3926703708 in QWidget::~QWidget() ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x00007f3926863fc9 in QStackedWidget::~QStackedWidget() ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x00007f3924f7228b in QObjectPrivate::deleteChildren() ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f3926703708 in QWidget::~QWidget() ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x00007f39267038d9 in QWidget::~QWidget() ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x00007f3924f7228b in QObjectPrivate::deleteChildren() ()
---Type <return> to continue, or q <return> to quit---
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00007f3926703708 in QWidget::~QWidget() ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x00000000013cf8b8 in flightgear::runLauncherDialog ()
at /home/mifi/Software/Sources/fgfs53/next/flightgear/src/GUI/QtLauncher.cxx:418
#26 0x000000000080d70d in fgMainInit (argc=3, argv=0x7ffe629e1378)
at /home/mifi/Software/Sources/fgfs53/next/flightgear/src/Main/main.cxx:545
#27 0x00000000007ba887 in main (argc=3, argv=0x7ffe629e1378)
at /home/mifi/Software/Sources/fgfs53/next/flightgear/src/Main/bootstrap.cxx:341


mifi
mifi
 
Posts: 327
Joined: Mon Jul 23, 2007 4:24 pm
Location: NL
Version: git next
OS: Ubuntu 18.04.x Gnome

Re: Segfault in launcher?

Postby wkitty42 » Wed Mar 21, 2018 7:45 pm

mifi wrote in Wed Mar 21, 2018 11:55 am:
can you do us a favor, too, please? go to the user control panel and update your profile with your OS and such so that it shows up in the right hand pane like you can see on my posts... that way we don't always have to ask someone what their system specs are if we forget...


Done.
I did not see a setting to make the 'system' show up in the right column, but it is in my profile now.

thanks! yeah, there's not a setting for "system" to show up on the right... not that we mere users have access to ;)

on your backtrace, i think that's what james/zakelaw was speaking of in the dev list earlier today... if it is the same thing, crash after clicking the [Fly!] button, here's what he wrote after someone provided him with another backtrace...

Okay that’s sort-of-expected, it seems to happen with some versions of Qt and will be fixed when the launcher is fully converted - which is what I’m pushing towards now. I also expect when it’s no longer a widgets-and-QtQuick hybrid the performance problems will go away, which is why I’m not focusing on them for now, but rather on getting the remaining two screens converted - AddOns is about half done now, location will be a little more work :)

Good news is various pieces of the UI flow are getting nicer along the way. And then the whole thing needs to be styled properly, right now it’s only programmer art, fortunately I know a designer or two :D

Kind regards,
James


i'll post your's over there and ask if it is the same thing... it likely is at this point...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 9146
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: Segfault in launcher?

Postby mifi » Thu Mar 22, 2018 8:52 am

i'll post your's over there and ask if it is the same thing... it likely is at this point...


Thanks. It looks like we will just have to wait a bit. No problem.
It is nice to know what is going on, so thanks again you for your intervention.

mifi
mifi
 
Posts: 327
Joined: Mon Jul 23, 2007 4:24 pm
Location: NL
Version: git next
OS: Ubuntu 18.04.x Gnome

Re: Segfault in launcher?

Postby wkitty42 » Thu Mar 22, 2018 7:19 pm

you're quite welcome :)
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 9146
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: Segfault in launcher?

Postby mifi » Thu Mar 22, 2018 7:57 pm

I noticed this commit:

The following commit(s) were added to refs/heads/next by this push:
new 28d8317 Work-arounds for launcher crashes on ‘fly’
28d8317 is described below
Work-arounds for launcher crashes on ‘fly’
Two are enabled, one is disabled for people to test.


And that seems to work fine. The segfault is gone.
Thanks James Turner.
mifi
mifi
 
Posts: 327
Joined: Mon Jul 23, 2007 4:24 pm
Location: NL
Version: git next
OS: Ubuntu 18.04.x Gnome

Next

Return to Support

Who is online

Users browsing this forum: No registered users and 4 guests