591503 - Seamonkey crashes when closing tabs (gecko 1.9.1.11 + cairo 1.8.10)

Status: RESOLVED DUPLICATE of bug 522635

(Core :: Graphics, defect)

Description

[Mason]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.11) Gecko/20100720 Fedora/2.0.6-1.fc13 SeaMonkey/2.0.6
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.11) Gecko/20100720 Fedora/2.0.6-1.fc13 SeaMonkey/2.0.6

Related bugs: bug 522635 and bug 557785
cf. also https://bugzilla.redhat.com/show_bug.cgi?id=602437


Reproducible: Always

Steps to Reproduce:
First make sure Seamonkey is set up to load http://www.google.com/
when a new tab is opened.

1. Start Seamonkey
2. Hit Ctrl+T 5 times in a row (open  5 tabs)
3. Hit Ctrl+W 2 times in a row (close 2 tabs)
4. Hit Ctrl+T 2 times in a row (open  2 tabs)
5. Hit Ctrl+Q (quit Seamonkey)
6. Hit Q to quit without saving
7. Crash

Comment 1

[Mason]

Attachment: Back trace for the proposed test case

The string "RenderBadPicture (invalid Picture parameter)" mentioned in bug 557785 shows up in frame #7

Comment 2

[Mason]

Another way to make Seamonkey crash in a slightly different way:

First make sure Seamonkey is set up to load http://www.google.com/
when a new tab is opened.

1. Hit Ctrl+T 5 times in a row (open 5 tabs)
2. Hit Ctrl+W 5 times in a row (close the 5 tabs)

Repeat 3-5 times until Seamonkey crashes.

Comment 3

[Martin Stránský [:stransky] (ni? me)]

Yes, I can confirm it. Fedora 13/x86_64/system cairo (cairo-1.8.10-1.fc13).

Comment 4

[Robert Kaiser]

This really is a crash with cairo, so it's no SeaMonkey bug.

It also doesn't happen with default builds, because they don't use system cairo. And actually, I think this should be considered a Fedora bug and not a Mozilla bug.

Comment 5

[Mason]

Hello Robert,

Your nick is kairo, do you have any relationship with the cairo project?

> This really is a crash with cairo, so it's no SeaMonkey bug.

(To be precise, cairo does not crash, it aborts.)

Are you saying there is a bug in cairo 1.8.10, which is not in 1.8.8?

(AFAIU, the bug is in gecko 1.9.1, not in cairo.)

> It also doesn't happen with default builds, because they don't use
> system cairo.

By "they" do you mean the gecko devs? the cairo integrators?

When you work on Seamonkey, do you take the toolkit part (gecko/cairo) as is?
Or do you tweak these parts?

> And actually, I think this should be considered a Fedora bug and not a
> Mozilla bug.

Could you explain why you think that?

If it's a Fedora bug, then it's also a Ubuntu bug, a Debian bug, and a Suse bug.
Do you think that these distributions should not use the system-wide cairo?

Regards.

Comment 6

[Mason]

This comment by Karl Tomlinson seems relevant.
https://bugzilla.mozilla.org/show_bug.cgi?id=522635#c8

Should this bug's component be Widget: Gtk?

Comment 7

[Robert Kaiser]

(In reply to comment #5)
> Your nick is kairo, do you have any relationship with the cairo project?

No, my nick comes from my real name, and I have no idea how that other project came to its name, what I know is they did it a long time after I had that nick already.

> Are you saying there is a bug in cairo 1.8.10, which is not in 1.8.8?

No, it sounds like an incompatibility with system cairo and the Mozilla platform version you are using. In that case, the correct workaround is to not use the system cairo.

> > It also doesn't happen with default builds, because they don't use
> > system cairo.
> 
> By "they" do you mean the gecko devs? the cairo integrators?

No, "they" are "the default builds" in this sentence.

> When you work on Seamonkey, do you take the toolkit part (gecko/cairo) as is?

We take exactly what is in the Mozilla platform, without a single change.

> > And actually, I think this should be considered a Fedora bug and not a
> > Mozilla bug.
> 
> Could you explain why you think that?

Because a bug that doesn't happen with the default builds we provide is not our bug, usually.

> If it's a Fedora bug, then it's also a Ubuntu bug, a Debian bug, and a Suse
> bug.

No. I haven't heard any reports of this happening with any distro not using the system cairo with Gecko 1.9.1. And if they do, they are on their own and it's their duty to make it work.

(In reply to comment #6)
> This comment by Karl Tomlinson seems relevant.
> https://bugzilla.mozilla.org/show_bug.cgi?id=522635#c8
> 
> Should this bug's component be Widget: Gtk?

Ask Karl, not me. I just know this bug is not in SeaMonkey code, and that's what I care about.

Comment 8

[Robert Kaiser]

(In reply to comment #7)
> I just know this bug is not in SeaMonkey code

...in SeaMonkey-specific code...

is what I wanted to say.

If it's in Mozilla code, it's in platform code, and that is not in my responsibility.

Comment 9

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

This is almost certainly due to bug 590591, that jeff keeps promising to fix.

Comment 10

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

(oh, gecko 1.9.1, maybe not, but still might be similar!)

Comment 12

[Mason]

Attachment: Back trace for seamonkey --sync

I've attached the back-trace I get when X calls are synchronous.

$ seamonkey --sync

Gdk-ERROR **: The program 'seamonkey-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
  (Details: serial 56846 error_code 156 request_code 147 minor_code 7)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
/usr/lib64/seamonkey-2.0.6/run-mozilla.sh: line 131:  1654 Aborted                 (core dumped) "$prog" ${1+"$@"}