The International Simutrans Forum

Simutrans Extended => Simutrans-Extended bug reports => Simutrans-Extended development => Simutrans-Extended closed bug reports => Topic started by: Vladki on January 25, 2017, 10:03:03 PM

Title: cannot resize window [f49e8a1]
Post by: Vladki on January 25, 2017, 10:03:03 PM
Hello,

with the latest Linux 64-bit (SDL) build I cannot resize game window. If i do, it stays black forever, and the game has to be killed with kill -9

Debug output has nothing unusual:
expose: x=708, y=560
textur_resize()::screen=0x2444f50
expose: x=729, y=560
textur_resize()::screen=0x2444f50


Title: Re: cannot resize window [f49e8a1]
Post by: jamespetts on January 25, 2017, 11:15:43 PM
That is very odd. It will be difficult for me to track this down as my main development machine runs Windows. Can you try compiling it in SDL2 instead to see whether this helps?
Title: Re: cannot resize window [f49e8a1]
Post by: Vladki on January 26, 2017, 10:55:12 PM
I have tried SDL 1 and 2 with latest commit 3071c0355287...
SDL1 - hangs (same as previous commit)
SDL2 - handful of different errors:
a) segfault
b) *** Error in `/home/vladki/simutrans/simutrans-experimental': double free or corruption (!prev): 0x0000000000e122c0 ***
c) simutrans-experimental: malloc.c:3524: _int_malloc: Assertion `(bck->bk->size & 0x4) == 0' failed.
Moreover SDL2 is really ugly, compare the screenshots:
(http://server.exp.simutrans.com/screenshots/sdl1.png)
(http://server.exp.simutrans.com/screenshots/sdl2.png)
Title: Re: cannot resize window [f49e8a1]
Post by: jamespetts on January 27, 2017, 01:22:19 AM
It is difficult for me to test this, but I have updated the SDL and SDL2 code to match the latest code in Standard. Are you able to test this? I should be most grateful.
Title: Re: cannot resize window [f49e8a1]
Post by: Vladki on January 30, 2017, 09:19:37 PM
It is OK now, thank you very much
Title: Re: cannot resize window [f49e8a1]
Post by: jamespetts on January 30, 2017, 09:20:59 PM
Excellent - glad that this worked. Thanks goes  to the Standard developers, too, of course, for writing the code that I incorporated.