Author Topic: [fixed] MegaGlest is a long time about closing 8-10 seconds.  (Read 1420 times)

Coldfusionstorm

  • Golem
  • ******
  • Posts: 868
    • View Profile
These are the logs

http://www.pasteall.org/39130   network.log

http://speedy.sh/HhPzV/debug.7z debug.log

and the glest.log was empty except for
Log file

Core data

What i did.

I started the game went to internet lobby joined a headless and disconnected and returned to main menu and clicked exit.

(Well f***** **** ****** ***).

(Edit for information i FORGOT).

Win7 64 Bit
SVN version 4057.
(and just in case I got it from the SVN and compiled it myself).
« Last Edit: 24 May 2013, 03:30:32 by tomreyn »
WiP Game developer.
I do danish translations.
"i break stuff"

Omega

  • MegaGlest Team
  • Dragon
  • ********
  • Posts: 6,167
  • Professional bug writer
    • View Profile
    • Personal site
Re: Megaglest is a long time about closing 8-10 seconds.
« Reply #1 on: 25 January 2013, 18:30:05 »
Do you even read the "READ THIS FIRST"? Version of MegaGlest? Operating system? Download location?
Edit the MegaGlest wiki: http://docs.megaglest.org/

My personal projects: http://github.com/KatrinaHoffert

Coldfusionstorm

  • Golem
  • ******
  • Posts: 868
    • View Profile
Re: Megaglest is a long time about closing 8-10 seconds.
« Reply #2 on: 26 January 2013, 12:42:45 »
I edited the first port to contain the information i forgot.
WiP Game developer.
I do danish translations.
"i break stuff"

tomreyn

  • Local Moderator
  • Airship
  • ********
  • Posts: 2,764
    • View Profile
    • MegaGlest - the free and open source cross platform 3D real-time strategy game
Re: Megaglest is a long time about closing 8-10 seconds.
« Reply #3 on: 26 January 2013, 14:20:43 »
This only happens when a network connection has been established, but then it takes, in my Windows 7 VM, (roughly) 15 seconds to shut down.
So I assume it is the winsock cleanup which takes a while. I guess it may be possible to background the process (or return to operation in non-graphical mode)  while it keeps shutting down the socket so the user can continue with something else in the meantime.

Another approach my be to just ignore the socket state and have the operating system on both ends of the connection deal with closing the connection and liberating the socket (I would think it does this generally, based on a timeout) on application exit (only). This can seem programmatically dirty but I assume that's how many other applications (not) handle it, too.
atibox: Ryzen 1800X (8 cores @3.6GHz), 32 GB RAM, MSI Radeon RX 580 Gaming X 8G, PCI subsystem ID [1462:3417], (Radeon RX 580 chipset, POLARIS10) @3440x1440; latest stable Ubuntu release, (open source) radeon (amdgpu) / mesa video driver
atibox (old): Core2Quad Q9400 (4 cores @2.66GHz), 8 GB RAM, XFX HD-467X-DDF2, PCI subsystem ID [1682:2931], (Radeon HD 4670, RV730 XT) @1680x1050; latest stable Ubuntu release, (open source) radeon / mesa video driver
notebook: HP envy13d020ng
internet access: VDSL2+

· · · How YOU can contribute to MG · Latest development snapshot · How to build yourself · Megapack techtree · Currently hosted MG games · · ·

Omega

  • MegaGlest Team
  • Dragon
  • ********
  • Posts: 6,167
  • Professional bug writer
    • View Profile
    • Personal site
Re: Megaglest is a long time about closing 8-10 seconds.
« Reply #4 on: 26 January 2013, 17:23:38 »
Confirmed. MegaGlest closed in about a second while in the custom game screen, but took about ten seconds to close after joining one of the master servers.
Edit the MegaGlest wiki: http://docs.megaglest.org/

My personal projects: http://github.com/KatrinaHoffert

softcoder

  • MegaGlest Team
  • Battle Machine
  • ********
  • Posts: 2,239
    • View Profile
Re: Megaglest is a long time about closing 8-10 seconds.
« Reply #5 on: 5 February 2013, 06:15:54 »
Not much can be done, the first time the IRC client connects to the IRC server it takes time. If you start and close the game before we can close the login process to the IRC server you have to wait for it to a) finish or b) abort.

titi

  • MegaGlest Team
  • Airship
  • ********
  • Posts: 4,240
    • View Profile
    • http://www.titusgames.de
Re: Megaglest is a long time about closing 8-10 seconds.
« Reply #6 on: 3 May 2013, 10:39:09 »
A hard system exit is not possible here ?
Try Megaglest! Improved Engine / New factions / New tilesets / New maps / New scenarios

Coldfusionstorm

  • Golem
  • ******
  • Posts: 868
    • View Profile
Re: Megaglest is a long time about closing 8-10 seconds.
« Reply #7 on: 3 May 2013, 14:58:55 »
Other games are able to close so, it's possible somehow, what about having a "close button" function call, alt-f4, ect, When activated just hard killing all processes or just hard killing network processes or stuff like that.
WiP Game developer.
I do danish translations.
"i break stuff"

softcoder

  • MegaGlest Team
  • Battle Machine
  • ********
  • Posts: 2,239
    • View Profile
Re: Megaglest is a long time about closing 8-10 seconds.
« Reply #8 on: 3 May 2013, 23:12:42 »
Found a way to do it, fixed in svn rev#: 4259

Coldfusionstorm

  • Golem
  • ******
  • Posts: 868
    • View Profile
Re: Megaglest is a long time about closing 8-10 seconds.
« Reply #9 on: 4 May 2013, 08:09:52 »
Exelent!, I will check it out!. (Might take some some time, need to get my game to compile again).
WiP Game developer.
I do danish translations.
"i break stuff"

tomreyn

  • Local Moderator
  • Airship
  • ********
  • Posts: 2,764
    • View Profile
    • MegaGlest - the free and open source cross platform 3D real-time strategy game
Re: Megaglest is a long time about closing 8-10 seconds.
« Reply #10 on: 17 May 2013, 23:31:16 »
Have you had a chance to test this, yet, Coldfusionstorm?
Anyone else on Windows?
atibox: Ryzen 1800X (8 cores @3.6GHz), 32 GB RAM, MSI Radeon RX 580 Gaming X 8G, PCI subsystem ID [1462:3417], (Radeon RX 580 chipset, POLARIS10) @3440x1440; latest stable Ubuntu release, (open source) radeon (amdgpu) / mesa video driver
atibox (old): Core2Quad Q9400 (4 cores @2.66GHz), 8 GB RAM, XFX HD-467X-DDF2, PCI subsystem ID [1682:2931], (Radeon HD 4670, RV730 XT) @1680x1050; latest stable Ubuntu release, (open source) radeon / mesa video driver
notebook: HP envy13d020ng
internet access: VDSL2+

· · · How YOU can contribute to MG · Latest development snapshot · How to build yourself · Megapack techtree · Currently hosted MG games · · ·

Coldfusionstorm

  • Golem
  • ******
  • Posts: 868
    • View Profile
Re: [testing] MegaGlest is a long time about closing 8-10 seconds.
« Reply #11 on: 18 May 2013, 19:34:03 »
Last i checked i couldn't compile the game, and i haven't had time to get it to work yet sorry.
WiP Game developer.
I do danish translations.
"i break stuff"

tomreyn

  • Local Moderator
  • Airship
  • ********
  • Posts: 2,764
    • View Profile
    • MegaGlest - the free and open source cross platform 3D real-time strategy game
Re: [testing] MegaGlest is a long time about closing 8-10 seconds.
« Reply #12 on: 24 May 2013, 03:30:12 »
I think Coldfusionstorm said on IRC he considers this [fixed] now. And so do I.
atibox: Ryzen 1800X (8 cores @3.6GHz), 32 GB RAM, MSI Radeon RX 580 Gaming X 8G, PCI subsystem ID [1462:3417], (Radeon RX 580 chipset, POLARIS10) @3440x1440; latest stable Ubuntu release, (open source) radeon (amdgpu) / mesa video driver
atibox (old): Core2Quad Q9400 (4 cores @2.66GHz), 8 GB RAM, XFX HD-467X-DDF2, PCI subsystem ID [1682:2931], (Radeon HD 4670, RV730 XT) @1680x1050; latest stable Ubuntu release, (open source) radeon / mesa video driver
notebook: HP envy13d020ng
internet access: VDSL2+

· · · How YOU can contribute to MG · Latest development snapshot · How to build yourself · Megapack techtree · Currently hosted MG games · · ·

 

anything