Author Topic: [invalid] MG 3.6.1-dev crashes on Fedora 17 when returning to fullscreen  (Read 1054 times)

jammyjamjamman

  • Administrator
  • Horseman
  • ********
  • Posts: 210
    • View Profile
When I want to switch from windowed mode to full-screen (by pressing alt+return) at any time during using the game it crashes, on both the Normal and the dev game.

Here is a link to a verbose log of the event in MG v3.6.03, although it is harder to achieve the crash when mg is opened in the terminal when returning to full-screen:http://megaglest.pzt.me/1ked

Also here is some information about my system created by the system report utility: http://megaglest.pzt.me/29er

I hope these links can be of help. :)
« Last Edit: 14 September 2012, 00:04:59 by tomreyn »
"All right, I've been thinking. When life gives you lemons? Don't make lemonade. Make life take the lemons back! Get mad! 'I don't want your damn lemons! What am I supposed to do with these?'" ~Cave Johnson, Portal 2

tomreyn

  • Local Moderator
  • Airship
  • ********
  • Posts: 2,764
    • View Profile
    • MegaGlest - the free and open source cross platform 3D real-time strategy game
Thanks for your report, Jammy.

This is more likely to be a graphics driver issue. Does it also happen with other OpenGL (3D) games/applications when switching between full screen and windowed mode?

It would be good to also have the log of a build of a current subversion revision, since error handling may have improved in that there can be more specific stack traces. Please consider posting it. (On a side note, it's -in most cases- better to produce error reports on the latest development code if that's an option.)

Before you run the game, please run ulimit -c unlimited so that a core dump (a file containing the entire memory region(s) MG used by the time it crashed) will be written when it crashes again. The core file is usually placed in the current working directory or in the same directory the binary exectuable file is located and its name startts with (or is) core. Please also report back whether you are able to produce this file by crashing.
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 · · ·

softcoder

  • MegaGlest Team
  • Battle Machine
  • ********
  • Posts: 2,239
    • View Profile
Please follow all the tomreyn said + please give stack traces and log files using svn head, is much more easy to follow a stack trace etc and that is where we would fix the bug also.

jammyjamjamman

  • Administrator
  • Horseman
  • ********
  • Posts: 210
    • View Profile
Ok thanks for the instructions.

With much help from tomreyn i managed to produce both these logs: http://megaglest.pzt.me/9keg, http://megaglest.pzt.me/3p3d

Also I should mention that sometimes this crash can cause the system to force me to log off or automatically do a reboot

tomreyn also mentioned to me:
Quote
<tomreyn> Jammyjamjamman: by unfortunate combination i mean that the two GPUs don't seem to go together well. generally mux-less  systems tend to be problematic.

So clearly it seems that the main problem here is the GPU set-up in this computer.
« Last Edit: 7 August 2012, 13:27:42 by jammyjamjamman »
"All right, I've been thinking. When life gives you lemons? Don't make lemonade. Make life take the lemons back! Get mad! 'I don't want your damn lemons! What am I supposed to do with these?'" ~Cave Johnson, Portal 2

softcoder

  • MegaGlest Team
  • Battle Machine
  • ********
  • Posts: 2,239
    • View Profile
Yes, the crash is coming from the video driver when mg is simply clearing the canvas. You'll need to try different versions of your video card driver to find one that is patched.

jammyjamjamman

  • Administrator
  • Horseman
  • ********
  • Posts: 210
    • View Profile
Sorry I've taken so long to reply.

Unfortunately, there were no working drivers for this computer with the particular GUI installed, and the alternate options (eg. using a different GUI, or replacing the GPU for a nvidia apparently works) are not options for me to decide, as i don't own this pc. But thanks for the help you all provided.  :)
"All right, I've been thinking. When life gives you lemons? Don't make lemonade. Make life take the lemons back! Get mad! 'I don't want your damn lemons! What am I supposed to do with these?'" ~Cave Johnson, Portal 2

tomreyn

  • Local Moderator
  • Airship
  • ********
  • Posts: 2,764
    • View Profile
    • MegaGlest - the free and open source cross platform 3D real-time strategy game
Thanks for your feedback. I'm tagging this as [invalid] since it's not a bug in MegaGlest.
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