(In reply to comment #160) > Typical, it appeared stable through my firefox testing, but if you try > reverting b7565a26401e283df94b68019e8093f8104428f4, I expect the corruptions > to disappear again.
Yep - correct revert of this commit make MAX_VERTEX 1 again producing correct rendering - even thought it's again noticable slower - thus now it's clear why I've considered it usable with MAX 1 before (in my comment 155). So yep - revert & MAX 1 works again - but it's quite slow. Is it now any better to deduce which operation is make such bad memory interaction ? It seems like the 'synchronization' is really needed only at very certain moments - where the GPU is producing memory corruption error on the screen - but how to catch in which moment ? I'm still suspecting some memory layout of those memory object - since when I see corruption - it usually it specific places (i.e. edit of this firefox input widget and just only certain characters at certain positions are render with errors) How can I try to increasing memory alignment ? (i.e. each object only at 16KB boundary?) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1098489 Title: [gen4] Corruption in Chrome omni bar results using Intel SNA To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1098489/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
