Board index FlightGear Support

The final reference count was ... crashing a lot now

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).

If you experience FlightGear crashes, please report a bug using the issue tracker (can be also used for feature requests).
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.

The final reference count was ... crashing a lot now

Postby asr » Sun Oct 15, 2017 9:56 am

Hi all,

Since I upgraded to 2017.3.1 I seem to be getting a lot of this crashes, to the point that FG is mostly unplayable.

I am using the same graphics configuration and system (macOS) I've been using for some years now, and never it crashed so much. Am I the only one experiencing this increased level of crashes?

This on the terminal where I run fgfs:

the final reference count was 1, memory corruption possible.

Illegal instruction: 4


Code: Select all
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.flightgear.FlightGear        0x0000000103fef6ab 0x1039cd000 + 6432427
1   libosg.130.dylib                 0x00000001055beb95 osg::NotifyStreamBuffer::sync() + 85
2   libosg.130.dylib                 0x00000001054f04bb std::__1::basic_ostream<char, std::__1::char_traits<char> >::flush() + 91
3   libosg.130.dylib                 0x00000001055daf2e osg::Referenced::~Referenced() + 430
4   libosg.130.dylib                 0x000000010556916e osg::Group::~Group() + 14
5   libosg.130.dylib                 0x00000001055db0de osg::Referenced::signalObserversAndDelete(bool, bool) const + 270
6   libosgDB.130.dylib               0x0000000105019a10 std::__1::__tree<std::__1::__value_type<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::pair<osg::ref_ptr<osg::Object>, double> >, std::__1::__map_value_compare<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::__value_type<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::pair<osg::ref_ptr<osg::Object>, double> >, std::__1::less<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >, true>, std::__1::allocator<std::__1::__value_type<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::pair<osg::ref_ptr<osg::Object>, double> > > >::erase(std::__1::__tree_const_iterator<std::__1::__value_type<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::pair<osg::ref_ptr<osg::Object>, double> >, std::__1::__tree_node<std::__1::__value_type<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::pair<osg::ref_ptr<osg::Object>, double> >, void*>*, long>) + 144
7   libosgDB.130.dylib               0x0000000105019048 osgDB::ObjectCache::removeExpiredObjectsInCache(double) + 216
8   libosgViewer.130.dylib           0x00000001053af279 osgViewer::Viewer::updateTraversal() + 281
9   libosgViewer.130.dylib           0x00000001053b4a5d osgViewer::ViewerBase::frame(double) + 109
10  org.flightgear.FlightGear        0x0000000103fedfee fgOSMainLoop() + 126
11  org.flightgear.FlightGear        0x0000000103a0f1db fgMainInit(int, char**) + 4635
12  org.flightgear.FlightGear        0x00000001039d5ff2 main + 290
13  org.flightgear.FlightGear        0x00000001039d5ce4 start + 52
asr
 
Posts: 58
Joined: Mon Sep 15, 2014 7:55 pm

Re: The final reference count was ... crashing a lot now

Postby erik » Mon Oct 30, 2017 9:50 am

Are you using prebuild binaries or are you compiling it yourself?
This link suggests incompatibilities between MacOS versions:
https://stackoverflow.com/questions/142 ... ion-min-10

Erik
erik
 
Posts: 1486
Joined: Thu Nov 01, 2007 1:41 pm

Re: The final reference count was ... crashing a lot now

Postby Hooray » Mon Oct 30, 2017 11:15 am

If possible, please share a screenshot showing your help/about dialog as well as the fgfs.log file in $FG_HOME


http://wiki.flightgear.org/About_dialog
http://wiki.flightgear.org/Commonly_use ... s#fgfs.log
Please don't send support requests by PM, instead post your questions on the forum so that all users can contribute and benefit
Thanks & all the best,
Hooray
Help write next month's newsletter !
pui2canvas | MapStructure | Canvas Development | Programming resources
Hooray
 
Posts: 11100
Joined: Tue Mar 25, 2008 8:40 am

Re: The final reference count was ... crashing a lot now

Postby BEL ISAAK » Thu Jan 11, 2018 10:55 am

I just experienced a similar crash on Win10.
fgfs.log
help-about.png

I'm using a multi-screen setup driven by two GPU's, but because of bad experiences I 'm not using multi-threading.

Edit: red box:
- Windows 10
- FlightGear 2017.3.1
- 2x Nvidia GeForce GTX 780Ti
- I 've only experienced this issue once, in the 777, while climbing out of VVTS for a flight to LFPG
- 777 is the FGaddon version
User avatar
BEL ISAAK
 
Posts: 159
Joined: Sat Jun 04, 2011 2:52 pm
Location: Leuven, Belgium
Callsign: OO-ISA
Version: 2017.3.1
OS: Windows


Return to Support

Who is online

Users browsing this forum: No registered users and 4 guests