(In reply to comment #38)
> The back trace you provide in your original report is different from the one I
> attached in bug 591503. Are you confident it is the same bug?
The one attached to bug 591503 is not from running the app with --sync and doesn't have enough information to confirm it is the same bug.
But I'm confident that Gecko 1.9.1 with system-cairo > 1.8.8 will display this bug.
> Should this
> bug be REOPENED with Version set to "1.9.1 branch" or should bug 591503 be used
> to track the progress of fixing the 1.9.1 branch?
Neither. This bug will track the status on 1.9.1 branch until the status-1.9.1 flag changes.
(In reply to comment #38)
> The back trace you provide in your original report is different from the one I
> attached in bug 591503. Are you confident it is the same bug?
The one attached to bug 591503 is not from running the app with --sync and doesn't have enough information to confirm it is the same bug.
But I'm confident that Gecko 1.9.1 with system-cairo > 1.8.8 will display this bug.
> Should this
> bug be REOPENED with Version set to "1.9.1 branch" or should bug 591503 be used
> to track the progress of fixing the 1.9.1 branch?
Neither. This bug will track the status on 1.9.1 branch until the status-1.9.1 flag changes.