#484 x128 crashes (rendering in double size is broken)

v2.4.x
closed-fixed
None
Windows
User Interface
2016-02-27
2013-12-11
Querino
No

newer builds of x128.exe crash as soon as they are fired up:

an unexpected error occured. received signal 11

what VICE version are you using? WinVICE-2.4.5-x86-r27847
what operating system are you using? Win7
what did you do? launch x128 :)
what did happen? crashed
what did you expect to happen? hehe, the obvious...

cool stuff, thanks :)

Discussion

  • gpz

    gpz - 2013-12-11

    i cant reproduce this on linux (2.4.5, rev 27691) so perhaps some windows specific problem

     
  • Querino

    Querino - 2013-12-12

    i checked, it was an entry in my vice.ini

    as soon as VDCDoubleSize is set to 1 there, that error occurs.

    but also, if you start x128.exe and set it manually in the menu
    options -> VDC settings -> double size

    xcbm2.exe crashes too when "double size" is true.
    i'd say xcbm2.exe starts in double size mode anyways, even if that
    value isn't set.

     
  • gpz

    gpz - 2013-12-12

    for those videochips the rendering was slightly changed... there is a "vertical stretch" option now, which basically does what doublesize did before (and indeed, it is enabled by default). the actual doublesize option now works the same as in the other emulators, ie it actually makes the window twice as big (not just stretch one axis).

    that said, it works fine for me in linux

     
  • Greg King

    Greg King - 2013-12-13

    It works fine for me, too. I tested that revision of the "nightly builds" on WinXP and Win7. I set VDCDoubleSize and CrtcDoubleSize to 1 in the configuration file. Neither x128 nor xcbm2 crashed.

    Maybe, it's an interaction with some other setting.

     
  • Querino

    Querino - 2013-12-13

    i gave it a try again.

    it DOES work here as well on my desktop machine, but NOT on my laptop.
    maybe because the double sized window exceeds the monitor resolution.
    but that is just a wild guess

     
  • Olaf Seibert

    Olaf Seibert - 2013-12-29

    I think it probably requires a few more settings for the problem to appear. I could reliably force a crash with the following combination:

    xpet -default -model 8032 -Crtcdsize -Crtchwscale -CRTCstretchvertical
    or
    xcbm2 -default -Crtcdsize -Crtchwscale -CRTCstretchvertical

    All those settings were required (changing any single one of them avoided the problem). Other rendering-related settings seemed to make no difference.

    "x128 -VDCdsize -VDChwscale -VDCstretchvertical" doesn't seem to do the same for me (I tried only twice) , but I noticed different GUIs behave slightly differently anyway. Running VICE under valgrind (a very good memory checker) shows the problem more often.

    I initially found the issue with the Xaw GUI but since I see it with the GTK GUI too, it probably isn't (just) the task of the Xaw maintainer (i.e. me) to fix this.

     
    Last edit: Olaf Seibert 2013-12-29
  • gpz

    gpz - 2014-01-28

    for some reason i could reproduce now, something must have changed in my system =) r27901 should fix it, please try again. also please verify that it works regardless of CRT emulation being used or not.

     
  • Querino

    Querino - 2014-01-29

    yes, this seems to do the trick, at least here using win7 and just the VDC on double size.

     
  • Marco van den Heuvel

    • status: pending-fixed --> closed-fixed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks