Crash [build 2016-01-09.e7887b8]
Moderator: Oberlus
Crash [build 2016-01-09.e7887b8]
Doesn't seem to matter if started from a save or a brand new game, go to one of the other screens (tried with research, production, design) then simply click the icon again and use the scroll wheel on the mouse to zoom out, crashes with a segmentation fault. Have tried quick start even end turn a couple of times, still happens.
Anyone else seeing this or does it just seem to be me?
Anyone else seeing this or does it just seem to be me?
Re: Crash [build 2016-01-09.e7887b8]
Not reproducible on OSX.
- The Silent One
- Graphics
- Posts: 1051
- Joined: Tue Jul 01, 2003 8:27 pm
Re: Crash [build 2016-01-09.e7887b8]
Can't reproduce on Win7.
If I provided any images, code, scripts or other content here, it's released under GPL 2.0 and CC-BY-SA 3.0.
- Geoff the Medio
- Programming, Design, Admin
- Posts: 12861
- Joined: Wed Oct 08, 2003 1:33 am
- Location: Munich
Re: Crash [build 2016-01-09.e7887b8]
Could you describe the steps to produce this crash more precisely / detailed?AndrewW wrote:...from a save or a brand new game, go to one of the other screens (tried with research, production, design) then simply click the icon again and use the scroll wheel on the mouse to zoom out, crashes with a segmentation fault.
Re: Crash [build 2016-01-09.e7887b8]
Starting a new game, doesn't seem to matter how, also happens on a saved game (was just finishing with one when it happened).Geoff the Medio wrote:Could you describe the steps to produce this crash more precisely / detailed?
Then just click on say the research icon, click on it again to go back to the map, zoom out with the mouse scroll wheel a bit and at least here it then crashes with a segmentation fault.
Might be it's specific to Linux, or perhaps just me for some reason. But have reproduced it multiple times here.
Re: Crash [build 2016-01-09.e7887b8]
Enabled verbose logging, last part of the freeoriond.log:
Code: Select all
2016-01-12 01:42:11.283169 [debug] Server : ... no orders from empire id: 1
2016-01-12 01:42:11.283178 [debug] Server : ... have orders from empire id: 2
2016-01-12 01:42:11.283186 [debug] Server : ... have orders from empire id: 3
2016-01-12 01:42:11.283194 [debug] Server : ... have orders from empire id: 4
2016-01-12 01:42:16.116527 [debug] Server : ServerNetworking::DisconnectImpl : disconnecting player 1
2016-01-12 01:42:16.116603 [debug] Server : ServerFSM::HandleNonLobbyDisconnection : Lost connection to player #1, named "Human_Player"; server terminating.
2016-01-12 01:42:16.116767 [debug] Server : ServerFSM::HandleNonLobbyDisconnection : All human players disconnected; server terminating.
2016-01-12 01:42:18.116880 [debug] Server : Initiating Exit (code 1 - error termination)
2016-01-12 01:42:18.116949 [debug] Server : ServerApp::CleanupAIs() telling AIs game is ending
2016-01-12 01:42:18.117109 [debug] Server : ServerApp::CleanupAIs() waiting 1 second for AI processes to clean up...
2016-01-12 01:42:19.117201 [debug] Server : ServerApp::CleanupAIs() killing 3 AI clients.
2016-01-12 01:42:19.117267 [debug] Server : Process::Kill
2016-01-12 01:42:19.117277 [debug] Server : Process::Kill calling m_impl->Kill()
2016-01-12 01:42:19.117285 [debug] Server : Process::Impl::Kill calling kill(m_process_id, SIGKILL)
2016-01-12 01:42:19.117305 [debug] Server : Process::Impl::Kill calling waitpid(m_process_id, &status, 0)
2016-01-12 01:42:19.117334 [debug] Server : Process::Impl::Kill done
2016-01-12 01:42:19.117342 [debug] Server : Process::Kill calling RequestTermination()
2016-01-12 01:42:19.117352 [debug] Server : Process::Impl::Kill calling kill(m_process_id, SIGKILL)
2016-01-12 01:42:19.117361 [debug] Server : Process::Impl::Kill calling waitpid(m_process_id, &status, 0)
2016-01-12 01:42:19.117381 [debug] Server : Process::Impl::Kill done
2016-01-12 01:42:19.117390 [debug] Server : Process::Kill
2016-01-12 01:42:19.117398 [debug] Server : Process::Kill calling m_impl->Kill()
2016-01-12 01:42:19.117406 [debug] Server : Process::Impl::Kill calling kill(m_process_id, SIGKILL)
2016-01-12 01:42:19.117415 [debug] Server : Process::Impl::Kill calling waitpid(m_process_id, &status, 0)
2016-01-12 01:42:19.117431 [debug] Server : Process::Impl::Kill done
2016-01-12 01:42:19.117438 [debug] Server : Process::Kill calling RequestTermination()
2016-01-12 01:42:19.117449 [debug] Server : Process::Impl::Kill calling kill(m_process_id, SIGKILL)
2016-01-12 01:42:19.117462 [debug] Server : Process::Impl::Kill calling waitpid(m_process_id, &status, 0)
2016-01-12 01:42:19.117475 [debug] Server : Process::Impl::Kill done
2016-01-12 01:42:19.117485 [debug] Server : Process::Kill
2016-01-12 01:42:19.117496 [debug] Server : Process::Kill calling m_impl->Kill()
2016-01-12 01:42:19.117509 [debug] Server : Process::Impl::Kill calling kill(m_process_id, SIGKILL)
2016-01-12 01:42:19.117522 [debug] Server : Process::Impl::Kill calling waitpid(m_process_id, &status, 0)
2016-01-12 01:42:19.117544 [debug] Server : Process::Impl::Kill done
2016-01-12 01:42:19.117555 [debug] Server : Process::Kill calling RequestTermination()
2016-01-12 01:42:19.117566 [debug] Server : Process::Impl::Kill calling kill(m_process_id, SIGKILL)
2016-01-12 01:42:19.117576 [debug] Server : Process::Impl::Kill calling waitpid(m_process_id, &status, 0)
2016-01-12 01:42:19.117590 [debug] Server : Process::Impl::Kill done
Re: Crash [build 2016-01-09.e7887b8]
I was playing on 876b6f9, tested and it didn't happen to me, rebased and recompiled on the small chance it was in Geoff's most recent commit which is the only backend change since then (cd7cbf6) and still not happening. Distro/graphics/driver issue?
Mat Bowles
Any code or patches in anything posted here is released under the CC and GPL licences in use for the FO project.
Any code or patches in anything posted here is released under the CC and GPL licences in use for the FO project.
Re: Crash [build 2016-01-09.e7887b8]
Dunno...
Got another way of doing it:
Start FreeOrion.
Click on Quick Start.
Use the mouse scroll wheel to zoom all the way out.
Click on the research icon.
Crash.
Re: Crash [build 2016-01-09.e7887b8]
Not for me (Kubuntu with a Radeon graphics card)
Mat Bowles
Any code or patches in anything posted here is released under the CC and GPL licences in use for the FO project.
Any code or patches in anything posted here is released under the CC and GPL licences in use for the FO project.
Re: Crash [build 2016-01-09.e7887b8]
As that's most probably the UI on the client crashing, freeorion.log is the relevant log file we need. The server log won't help much I think.AndrewW wrote:Enabled verbose logging, last part of the freeoriond.log
Re: Crash [build 2016-01-09.e7887b8]
Here you go:Vezzra wrote:As that's most probably the UI on the client crashing, freeorion.log is the relevant log file we need. The server log won't help much I think.AndrewW wrote:Enabled verbose logging, last part of the freeoriond.log
Re: Crash [build 2016-01-09.e7887b8]
Debian and Nvidia here.MatGB wrote:Not for me (Kubuntu with a Radeon graphics card)
- Geoff the Medio
- Programming, Design, Admin
- Posts: 12861
- Joined: Wed Oct 08, 2003 1:33 am
- Location: Munich
Re: Crash [build 2016-01-09.e7887b8]
No crash for me on Windows.
It might help if you can provide a stack trace from when the crash occurred.
It might help if you can provide a stack trace from when the crash occurred.
Re: Crash [build 2016-01-09.e7887b8]
Here you go:Geoff the Medio wrote:It might help if you can provide a stack trace from when the crash occurred.
Started freeorion, went to Quick Start, started the trace, zoomed out and then clicked on the research icon.
- Geoff the Medio
- Programming, Design, Admin
- Posts: 12861
- Joined: Wed Oct 08, 2003 1:33 am
- Location: Munich
Re: Crash [build 2016-01-09.e7887b8]
I don't know what I'm looking at in that .trace file... it doesn't look like the usual stack traces that people post when diagnosing crashes...