Multithread sw render buffer overflow

Forum rules
Please construct and post a simple demo whenever possible for all bug reports. Please provide links to everything.

If you can include a wad demonstrating the problem, please do so. Bug reports that include fully-constructed demos have a much better chance of being investigated in a timely manner than those that don't.

Please make a new topic for every bug. Don't combine multiple bugs into a single topic. Thanks!

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies

BBCode is OFF
Smilies are ON

Topic review
   

Expand view Topic review: Multithread sw render buffer overflow

Re: Multithread sw render buffer overflow

by Rachael » Sat Mar 02, 2019 2:37 pm

These are very difficult to solve.

At one point, it was the fog boundaries causing it, and that was fixed, and while it did mitigate some of the crashing it did not fix all of it.

Multithread sw render buffer overflow

by Edward-san » Sat Mar 02, 2019 2:12 pm

The titlemap of Square1 makes GZDoom multithread sw renderer (except vid_rendermode 0) instantaneously crash with the address sanitizer, as seen below:
Spoiler:
I got the values of the args of the crashing function:

Code: Select all

(uint32_t) width = 32
(uint32_t) height = 32
(uint32_t) xone = 134217728
(uint32_t) yone = 134217728
(uint32_t) xstep = 39396284
(uint32_t) ystep = 0
(uint32_t) xfrac = 786861999
(uint32_t) yfrac = 1632337501
(const uint32_t *) source = 0x00006290018d2200

Top