-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'The connection to the server has been lost' in single player #3307
Comments
Please attach a save from a turn or two before this happens. It is very unlikely that the specific steps to reproduce are playing a newly started game with any settings for exactly 77 turns. What is displayed on the options window Directories tab? Is that directory writable by the FreeOrion binaries and the user you're running the game as? |
The directory is writable. I did upload a saved game previously -- or thought I did. It just happened to me again at turn 54 in a new game. x-special/nautilus-clipboard file:///home/stephen/.local/share/freeorion/save/save-20210211_201249.sav |
Not that I can see... Yor comment just has text for the local path where some files are located, but no file attachments. You might need to zip a .sav file for it to attach, but .log files attach OK for me. |
freeorion.log |
I believe I am getting the same bug: I can play for a while, but eventually the server segfaults, which causes the client to give a message saying the server connection has been lost. Here's a save right before the crash - all I have to do is advance to the next turn. And the gdb traceback for freeoriond when the crash happens:
Platform: Debian 10 AMD64. |
Where did you find that? I would go over my logs looking if I knew where to look. I'm experienced in general, but compilers and such are something I haven't used much. |
To find the process ID, in a terminal: ps axuw|grep freeoriond (or whatever the process ID was. Freeorion spawns several processes; freeoriond is the server.) gdb will pause the server when it attaches; 'c' and enter to resume. Play normally. If the daemon crashes, the debugger will pause the process and give the "Program received SIGSEGV" message. Then type 'bt' and enter to get the backtrace. If you don't have gdb installed, your package manager probably keeps it in a package called gdb. If #1 in the backtrace ISN'T (big hex number) SpeciesManager::GetSpecies(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&) () |
I'm gonna have to start a new game to be able to run the back trace. |
Okay, it seems like we're looking at the same thing. Backtrace:
|
I can't reproduce a crash with the provided saves with (nearly) the latest master. Might be compiler or OS specific. The provided logs appear to be from different runs of the client and server, so I'm not able to determine much from them. |
Let’s close it. I did some OS work and wasn’t seeing the issue after.
From: Geoff ***@***.***>
Sent: Wednesday, July 21, 2021 08:32
To: freeorion/freeorion ***@***.***>
Cc: S. W. Cohrs ***@***.***>; Author ***@***.***>
Subject: Re: [freeorion/freeorion] 'The connection to the server has been lost' in single player (#3307)
I can't reproduce a crash with the provided saves with (nearly) the latest master. Might be compiler or OS specific. The provided logs <#3307 (comment)> appear to be from different runs of the client and server, so I'm not able to determine much from them.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#3307 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK6S3SNBEAYRV23YPXNV2OTTY244PANCNFSM4XPV6ULQ> . <https://github.com/notifications/beacon/AK6S3SLTLVGJ4VCLN5JLVFTTY244PA5CNFSM4XPV6UL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGSZRUNQ.gif>
|
Bug Report
Environment
FreeOrion Version: 0.4.10+[build 2021-02-09.cb4b741]CMake
Operating System:SuSE LEAP 15.2 (New install on 2021-02-06)
Graphic card used:Radeon
Fetched as
Description
System does not appear to be creating logs in the indicated locationExpected Result
Steps to reproduce
The text was updated successfully, but these errors were encountered: