[necroslut]

EDuke32 crashed quietly upon loading this map ("E1L2" from Alien Invasion). The loading screen gets displayed, but it doesn't look to me like the progress bar starts moving. There's nothing out of the ordinary in the logs.
I've tried the map in DOS Duke (1.3D and 1.5), as well as an older EDuke (2018), and it works fine there. It's a TC map, but skipping the arts/cons make no difference to whether it crashes or not in any of the versions. I've also checked it in Mapster and there doesn't seem to be any corruptions.
Is this some known issue? I'm attaching the map file below.

Edit: running it in software mode it actually starts, running for a second or two before crashing. Still nothing that looks interesting in the logs (I've tried the debug build too). There's some GL warning earlier, no idea if it's related.
(" debug: DwmGetCompositionTimingInfo() FAILED! HRESULT: 0x80263001 (Unknown error) ")

Attached File(s)

•  E2L2.zip (50.68K)
  Number of downloads: 227

[LeoD]

necroslut, on 19 April 2020 - 06:06 AM, said:

[...] nothing that looks interesting in the logs (I've tried the debug build too).

Without the [crash] logs your issue report doesn't look interesting either...

[necroslut]

LeoD, on 19 April 2020 - 06:23 AM, said:

Without the [crash] logs your issue report doesn't look interesting either...

There's no "crash log" since nothing gets printed to it after the map loads. Here it is, anyway...

Attached File(s)

•  eduke32.log (3.88K)
  Number of downloads: 170

[LeoD]

necroslut, on 19 April 2020 - 07:17 AM, said:

There's no "crash log" since nothing gets printed to it after the map loads. Here it is, anyway...

Did you forget the debug DLL (ebacktrace1-64.dll)?
Just a few lines above this thread there's something you might want to read.
However, issue confirmed. My [crash]logs look like this:
 eduke32-E2L2-synthesis.log (2.29K)
Number of downloads: 164
 eduke32-E2L2-synthesis.crash.log (1.38K)
Number of downloads: 181
 eduke32-E2L2-leod.log (1.33K)
Number of downloads: 183
 eduke32-E2L2-leod.crash.log (2.4K)
Number of downloads: 168

[necroslut]

LeoD, on 19 April 2020 - 07:46 AM, said:

Did you forget the debug DLL (ebacktrace1-64.dll)?
Just a few lines above this thread there's something you might want to read.

Yes, I did... There's been a few years since I reported a bug. So, confirmed? Do you need any more information?

[LeoD]

necroslut, on 19 April 2020 - 07:57 AM, said:

Yes, I did... There's been a few years since I reported a bug.

I guess the debug DLL needs an extra mention in the Crash section of that wiki page. Done.

necroslut, on 19 April 2020 - 07:57 AM, said:

So, confirmed?

Definitely.

necroslut, on 19 April 2020 - 07:57 AM, said:

Do you need any more information?

Nope. It's not for me, btw., but for the actual developers. The better you deliver, the greater the chance for a fix.

Bisect-compiled to r7813-a78e49c23, aka r7820 in the old Subversion repository. Thanks to oasiz for pointing me into the right direction.
 eduke32-r7813-a78e49c23.log (1.42K)
Number of downloads: 157
 eduke32-r7813-a78e49c23.crash.log (2.74K)
Number of downloads: 184

[necroslut]

LeoD, on 19 April 2020 - 12:08 PM, said:

I guess the debug DLL needs an extra mention in the Crash section of that wiki page. Done.
Nope. It's not for me, btw., but for the actual developers. The better you deliver, the greater the chance for a fix.

Bisect-compiled to r7813-a78e49c23, aka r7820 in the old Subversion repository. Thanks to oasiz for pointing me into the right direction.

Ah, I got the impression you were a developer.
I was prepared to bisect and shit, but I wanted to know if it was a known issue already before I wasted the time.
For myself, I already "solved" it by using an older version.

[LeoD]

necroslut, on 19 April 2020 - 08:56 PM, said:

Ah, I got the impression you were a developer.

Not for software. But I know my way around hunting issues via brute force methods like bisecting, or the printf() debugger.

[Ninety-Six]

LeoD, on 20 April 2020 - 01:55 AM, said:

Not for software. But I know my way around hunting issues via brute force methods like bisecting, or the printf() debugger.

Out of curiosity, what is bisecting? (and from my thread, trisecting?)

[LeoD]

Ninety-Six, on 20 April 2020 - 03:17 AM, said:

Out of curiosity, what is bisecting? (and from my thread, trisecting?)

LeoD, on 19 April 2020 - 07:46 AM, said:

Just a few lines above this thread there's something you might want to read.

[LeoD]

It seems that r7813-a78e49c2 / svn7820 was a bad commit. It started causing a Mapster32 crash as well, which I've reported last month.

[necroslut]

Ok, this seems to be fixed now.