Notice: A non well formed numeric value encountered in /var/www/bugs.eduke32.com/includes/class.flyspray.php on line 105 Notice: A non well formed numeric value encountered in /var/www/bugs.eduke32.com/includes/class.flyspray.php on line 105 Notice: A non well formed numeric value encountered in /var/www/bugs.eduke32.com/includes/class.flyspray.php on line 105 FS#32 : r4897 introduces startup crash on some architectures

EDuke32

  • Status Unconfirmed
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Backend / Core
  • Assigned To No-one
  • Operating System Windows
  • Severity Critical
  • Priority Very Low
  • Reported Version Development
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: EDuke32
Opened by Martin Howe - 2016-10-02

FS#32 - r4897 introduces startup crash on some architectures

I have been using r5485 32 bit for some time on a modern laptop (i7, 12GB, Intel HD 4.3.0 / GTX 850) for some time. Copied EDuke32 installation to my backup laptop (i3, 4GB, very basic Intel graphics) and it crashes on startup. I get some OpenGL feature-not-present warnings, as expected for a machine of this age/class, but wasn’t expecting it to crash.

Bisected timeline using debug builds, change was introduced in r4897; previous build works fine. Tested with out-of-the-box install, no HRP, no addons, no settings changes. Extract, copy in atomic duke3d.grp, run eduke32, click start button in startup dialog making no settings changes whatever.

Crash log, CPU-Z and MSINFO32 reports attached.

Admin
Evan Ramos commented on 2016-10-02 10:37

The problem probably comes from r4891, and unfortunately is a bug in Intel's drivers if I understand it correctly.

Try building the program having removed the lines

<!-- Windows 10 -->
<supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>

from the manifest.*.xml files.

Martin Howe commented on 2016-10-02 14:39

Thanks. Built r5875 and got the crash, changed the manifest as instructed, rebuilt, no crash.

This issue was also reported for GZDoom and somebody on ZDoom forums made a .EXE patcher that patches the manifest.

Knowing little about device driver programming, I would ask: why exactly should removing that line fix the issue? And is that line really necessary given the game seems to run OK without it?

Admin
Evan Ramos commented on 2016-10-05 04:48
Martin Howe commented on 2016-10-05 08:46

Thanks. I guess you can close this thread now since there's nothing anybody can do.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing