MantisBT - Doomseeker
View Issue Details
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.
TagsNo tags attached.
Relationships
child of 0003279acknowledged  List of Debian issues (misc/non-policy) 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2017-06-20 06:20PolygonNew Issue
2017-06-20 06:21PolygonNote Added: 0017853
2017-06-20 06:22PolygonNote Edited: 0017853bug_revision_view_page.php?bugnote_id=17853#r10703
2017-06-21 00:20Ru5tK1ngNote Added: 0017856
2017-06-23 15:28PolygonNote Added: 0017887
2017-06-23 17:35Ru5tK1ngNote Added: 0017890
2017-06-23 17:56WaTaKiDNote Added: 0017892
2017-06-25 17:20PolygonNote Added: 0017920
2017-06-25 20:37DuskProjectZandronum => Doomseeker
2017-07-02 09:29ZalewaAssigned To => Zalewa
2017-07-02 09:29ZalewaStatusnew => assigned
2017-07-02 09:39ZalewaSeveritycrash => minor
2017-07-02 09:39ZalewaProduct Version3.0-beta =>
2017-07-03 16:49ZalewaNote Added: 0017976
2017-07-03 16:49ZalewaStatusassigned => needs review
2017-09-24 17:03ZalewaNote Added: 0018369
2017-09-24 17:03ZalewaStatusneeds review => needs testing
2017-09-24 17:34WubTheCaptainNote Added: 0018370
2017-09-24 17:38WubTheCaptainNote Added: 0018371
2017-09-24 17:40WubTheCaptainNote Edited: 0018371bug_revision_view_page.php?bugnote_id=18371#r11001
2017-09-24 17:40WubTheCaptainNote Edited: 0018371bug_revision_view_page.php?bugnote_id=18371#r11002
2017-09-24 17:42WubTheCaptainNote Edited: 0018371bug_revision_view_page.php?bugnote_id=18371#r11003
2017-09-24 17:43WubTheCaptainNote Edited: 0018371bug_revision_view_page.php?bugnote_id=18371#r11004
2017-09-24 17:45WubTheCaptainNote Edited: 0018371bug_revision_view_page.php?bugnote_id=18371#r11005
2017-09-24 17:47WubTheCaptainNote Edited: 0018371bug_revision_view_page.php?bugnote_id=18371#r11006
2017-09-24 17:51WubTheCaptainNote Edited: 0018371bug_revision_view_page.php?bugnote_id=18371#r11007
2017-09-24 18:04ZalewaStatusneeds testing => resolved
2017-09-24 18:04ZalewaFixed in Version => 1.2
2017-09-24 18:04ZalewaResolutionopen => fixed
2017-09-27 22:35WubTheCaptainRelationship addedchild of 0003279
2018-09-27 03:16WubTheCaptainTarget Version => 1.2
2018-10-27 22:55WubTheCaptainStatusresolved => closed

Notes
(0017853)
Polygon   
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.
(0017856)
Ru5tK1ng   
2017-06-21 00:20   
What version of Doomseeker are you using? If it's 1.1 does it crash old beta releases?
(0017887)
Polygon   
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?
(0017890)
Ru5tK1ng   
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.
(0017892)
WaTaKiD   
2017-06-23 17:56   
is the issue reproducible when the server is hosted without doomseeker? ie from command line
(0017920)
Polygon   
2017-06-25 17:20   
Confirmed on my end, It is not reproducible without doomseeker. This is definitely an issue with doomseeker.
(0017976)
Zalewa   
2017-07-03 16:49   
Fix:'https://bitbucket.org/Doomseeker/doomseeker/commits/acf3900026831e893f9c788e54192e2cd7e8bf55 [^]'
(0018369)
Zalewa   
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?
(0018370)
WubTheCaptain   
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.
(0018371)
WubTheCaptain   
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.