Comment 33 for bug 337608
Revision history for this message
|
|
#33 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
(In reply to comment #7)
> Yeah, I think the corruption I saw is due to migration code (or more
> specifically the dirty update stuff), but the crash must be due to either an
> unmap happing at the wrong time or the mapping size changing like you say. If
> you have a driver that doesn't manage pixmaps it's pretty easy to see the
> corruption with the default migration scheme (always I think?) at the Java test
> page referenced in this bug.
Does
Option "EXAOptimizeMig
work around the corruption? Also I'm having a hard time reproducing reports of problems with that option enabled with xserver master, can you reproduce it with that?
> I'd like to solve the problem properly as well, but I'll have to dig through
> the EXA code a lot more (I haven't looked at the migration or sys vs offscreen
> mapping code much at all).
It's not clear to me at this point it's an EXA bug at all... some values in the backtrace look way off, but the trace may just be inaccurate, or even if not the question is which layer would be responsible for sanitizing them.