http://bugs.winehq.org/show_bug.cgi?id=59732 --- Comment #27 from Rafał Mużyło <galtgendo@o2.pl> --- (In reply to Dmitry Timoshkov from comment #25)
Without a proper regression test guessing a component won't help much.
Ah, yes and no. While generally, 'going by the feels' isn't the right approach, at this point we should be at about 'reasonable cause' level. It could still be something else, but available evidence points strongly towards that commit series, at least when it comes to the glyph distortion. The 'extra bits' part is - going by the logs - a problem of a different sort, but someone with deep enough understanding of that code would still be helpful... (not to mentioned, that due to that crash, a proper bisect would be far from simple - first you need to establish which commit causes the crash, then create a branch with that commit merged into the one introducing the crashing code then rerun the bisect; that is unless you want to play pingpong with manually reapplying the commit each bisect step then resetting) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.