Comment 11 for bug 267297

Revision history for this message
In , Paulo Dias (paulo-miguel-dias) wrote :

(In reply to comment #10)
> (In reply to comment #8)
> > ok, the patch fixes the bug, changing bug status to fixed.
>
> That should only be done once the fix is applied to Git.

Yes, i updated to git and reapplied the patch. I thought the bug was fixed, unfortunately although is happens much less its STILL there.

Alex on IRC said it MIGHT be a memory allocation bug, and i tend to agree, since this bug can be triggered randomly in and out in the same X session .
>
>
> (In reply to comment #9)
> > unfortunatelly with latest git code 6cebfe257f7ddad855ee743e4eb899bd6fac7f46,
> > the bug appears OCASIONALLY with xv, reopening
>
> With the patch applied on top of that commit?

Yes. Sorry for the closing and reopening, i should have done more tests (i should known better :P) before closing this bug.