Marvin testbot@winehq.org wrote:
Same patch sent separately runs without failures: https://testbot.winehq.org/JobDetails.pl?Key=89342
On 4/26/21 7:53 AM, Dmitry Timoshkov wrote:
The tests crash with STATUS_HEAP_CORRUPTION, which strikes me as something that could cause inconsistent behaviour. Are you sure that you're not introducing a failure here?
"Zebediah Figura (she/her)" zfigura@codeweavers.com wrote:
Thanks for the hint. Running with warn+heap helped to find the reason of the heap corruption, it's 'p[GlobalSize(global)] = 0;' statements. This revealed another bug in msxml3 - it doesn't NUL terminate the stream on ::save(). After fixing that and removing 'p[] = 0' the processing instruction tests stopped to crash.
P.S. warn+heap still makes msxml3 domdoc tests crash, however that looks like another bug somewhere.
Dmitry Timoshkov dmitry@baikal.ru wrote:
That another crash happens at the end of test_get_ownerDocument() because priv->properties of doc1 and doc_owner have the same pointer value, and releasing doc_owner after doc1 leads to a double free and heap corruption.
Nikolay, could you please have a look?
On Tue, 27 Apr 2021 at 15:38, Dmitry Timoshkov dmitry@baikal.ru wrote:
I won’t have time for that in coming days.
-- Dmitry.
On 4/27/21 7:37 AM, Dmitry Timoshkov wrote:
That's a rather old bug; unfortunately it's been independently discovered several times by now...
On Tue, 27 Apr 2021, Dmitry Timoshkov wrote: [...]
I'm one of the rediscoverers and I (re)sent a patch: https://www.winehq.org/pipermail/wine-devel/2021-May/186299.html
Francois Gouget fgouget@codeweavers.com wrote:
Thanks for working on this! Still, I'm waiting for a review of this patchset from the maintainer. Nikolay, could you please either start reviewing assigned to you patches in a reasonable time frame, or stop pretending to be a maintainer?
On 5/6/21 5:41 PM, Dmitry Timoshkov wrote:
First you asked someone else to fix an older problem, that sort of blocks test results from your own patches, instead of fixing it yourself. Now you're complaining that it didn't happen fast enough?
Nikolay Sivov nsivov@codeweavers.com wrote:
No, I didn't ask someone else (who is that by the way?), I went ahead and debuugged the problem and sent an analysis to the list. Zebediah then replied: "That's a rather old bug; unfortunately it's been independently discovered several times by now..."
, that sort of blocks test results from your own patches, instead of fixing it yourself.
Do you mean that anyone sending patches must fix test failures caused intermittently by not related things in *existing* tests?
And you while being a manintainer were ignoring this old bug for years https://bugs.winehq.org/show_bug.cgi?id=43377 https://www.winehq.org/pipermail/wine-devel/2018-February/123378.html https://www.winehq.org/pipermail/wine-devel/2018-February/123379.html and now you're demanding me to fix that bug for you? That's rude and incompentent on your part, to say the least.
Now you're complaining that it didn't happen fast enough?
Are you really a maintainer, or just pretending to be the one?