Zandronum Chat on our Discord Server Get the latest version: 3.1
Source Code
My View | View Issues | Change Log | Roadmap | Doomseeker Issue Support Ranking | Rules | My Account
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0003159Doomseeker[All Projects] Bugpublic2017-06-20 06:202018-10-27 22:55
ReporterPolygon 
Assigned ToZalewa 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformLinuxOSLinux MintOS Version18.1
Product Version 
Target Version1.2Fixed in Version1.2 
Summary0003159: Server does not close cleanly
DescriptionWhen the server is closed (Tested via doomseeker)

Server crashes with the message "The server terminated unexpectedly with exit code: 9"
Steps To ReproduceCreate a server through doomseeker and then close the window.
Additional InformationLinux Mint is an Ubuntu Derivative which is a Debian derivative so this could be happening on other Debian variants as well.
Attached Files

- Relationships
child of 0003279acknowledged List of Debian issues (misc/non-policy) 

-  Notes
User avatar (0017853)
Polygon (reporter)
2017-06-20 06:21
edited on: 2017-06-20 06:22

 Keep in mind this is for Zandronum 3.0-r170618-1927

Only happens on close does not seem to negatively affect anything as far as hosting goes. This is just to make sure it's working okay.
User avatar (0017856)
Ru5tK1ng (updater)
2017-06-21 00:20

 What version of Doomseeker are you using? If it's 1.1 does it crash old beta releases?
User avatar (0017887)
Polygon (reporter)
2017-06-23 15:28

 I'm using version 1.1-170607-0236 for doomseeker

If you're asking if it crashes with older zandronum beta releases yes it does. So This must be a doomseeker issue?
User avatar (0017890)
Ru5tK1ng (updater)
2017-06-23 17:35

 I would say this is indeed a doomseeker issue. If this bug never happened with an older version of doomseeker, then the problem is from the 1.1 update.
User avatar (0017892)
WaTaKiD (updater)
2017-06-23 17:56

 is the issue reproducible when the server is hosted without doomseeker? ie from command line
User avatar (0017920)
Polygon (reporter)
2017-06-25 17:20

 Confirmed on my end, It is not reproducible without doomseeker. This is definitely an issue with doomseeker.
User avatar (0017976)
Zalewa (developer)
2017-07-03 16:49

 Fix:'https://bitbucket.org/Doomseeker/doomseeker/commits/acf3900026831e893f9c788e54192e2cd7e8bf55 [^]'
User avatar (0018369)
Zalewa (developer)
2017-09-24 17:03

 Wub, sorry for attaching you to an issue not reported by you, but you're very active and helpful. Could you verify this fix for us?
User avatar (0018370)
WubTheCaptain (reporter)
2017-09-24 17:34

 I believe I actually tested this issue yesterday – accidentally. I got an exit code error, but I believe that was because I pressed Meta + Shift + Q (shortcut in i3 window manager to close a window with a kill signal). My i3 isn't configured for kill -9, only a regular kill.

# kill focused window
bindsym $mod+Shift+q kill


If I type a server command to exit, it exits gracefully. The steps to reproduce are a little bit unclear how the server should be closed in this case.
User avatar (0018371)
WubTheCaptain (reporter)
2017-09-24 17:38
edited on: 2017-09-24 17:51

 I tested for real.

Meta + Shift + Q doesn't give an exit error in build 1d4d939a78e0 (latest Mercurial), with your commit included.

Meta + Shift + Q is an error in Doomseeker 1.1.

In 1d4d939a78e0 from a shell (in terminal emulator), kill -9 (SIGKILL) on the process ID still gives the exit error 9 as it should. kill (SIGTERM) gives exit error 15, this is the default signal.

Less relevant tests: Also in 1d4d939a78e0, kill -3 (SIGQUIT) also gives an an exit error 3. Ditto for SIGINT, exit error 2.

Issue Community Support
This issue is already marked as resolved.
If you feel that is not the case, please reopen it and explain why.
Supporters: No one explicitly supports this issue yet.
Opponents: No one explicitly opposes this issue yet.

- Issue History
Date Modified Username Field Change
2017-06-20 06:20 Polygon New Issue
2017-06-20 06:21 Polygon Note Added: 0017853
2017-06-20 06:22 Polygon Note Edited: 0017853 View Revisions
2017-06-21 00:20 Ru5tK1ng Note Added: 0017856
2017-06-23 15:28 Polygon Note Added: 0017887
2017-06-23 17:35 Ru5tK1ng Note Added: 0017890
2017-06-23 17:56 WaTaKiD Note Added: 0017892
2017-06-25 17:20 Polygon Note Added: 0017920
2017-06-25 20:37 Dusk Project Zandronum => Doomseeker
2017-07-02 09:29 Zalewa Assigned To => Zalewa
2017-07-02 09:29 Zalewa Status new => assigned
2017-07-02 09:39 Zalewa Severity crash => minor
2017-07-02 09:39 Zalewa Product Version 3.0-beta =>
2017-07-03 16:49 Zalewa Note Added: 0017976
2017-07-03 16:49 Zalewa Status assigned => needs review
2017-09-24 17:03 Zalewa Note Added: 0018369
2017-09-24 17:03 Zalewa Status needs review => needs testing
2017-09-24 17:34 WubTheCaptain Note Added: 0018370
2017-09-24 17:38 WubTheCaptain Note Added: 0018371
2017-09-24 17:40 WubTheCaptain Note Edited: 0018371 View Revisions
2017-09-24 17:40 WubTheCaptain Note Edited: 0018371 View Revisions
2017-09-24 17:42 WubTheCaptain Note Edited: 0018371 View Revisions
2017-09-24 17:43 WubTheCaptain Note Edited: 0018371 View Revisions
2017-09-24 17:45 WubTheCaptain Note Edited: 0018371 View Revisions
2017-09-24 17:47 WubTheCaptain Note Edited: 0018371 View Revisions
2017-09-24 17:51 WubTheCaptain Note Edited: 0018371 View Revisions
2017-09-24 18:04 Zalewa Status needs testing => resolved
2017-09-24 18:04 Zalewa Fixed in Version => 1.2
2017-09-24 18:04 Zalewa Resolution open => fixed
2017-09-27 22:35 WubTheCaptain Relationship added child of 0003279
2018-09-27 03:16 WubTheCaptain Target Version => 1.2
2018-10-27 22:55 WubTheCaptain Status resolved => closed




Questions or other issues? Contact Us.

Links

Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker