790144 - SVG "stroke" hangs SeaMonkey 2.12.x and Firefox 15.0.x. Regression.

Status: RESOLVED WORKSFORME

(Core :: General, defect)

Description

[Eddie Maddox]

Attachment: SVG-stroke-hang.svg - test case

User Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120715 Firefox/14.0.1 SeaMonkey/2.11
Build ID: 20120715044704

Steps to reproduce:

Attempt to display the attached local SVG file with SeaMonkey & Firefox.



Actual results:

" stroke="black" ", if present, causes the browser to hang in SeaMonkey 2.12.x,
but not in earlier versions. Likewise for the Firefox counterpart versions.



Expected results:

Line appears between the two text lines.
No browser hang.

Comment 1

[Robert Longson [:longsonr]]

Does it still hang with Aurora (16), Beta(17) or a nightly?

Comment 2

[Matthias Versen [:Matti]]

I can reproduce the hang with Firefox15 on linux 
it works with 
Firefox15 and Seamonkey trunk on windows
and
Mozilla/5.0 (X11; Linux i686; rv:18.0) Gecko/18.0 Firefox/18.0

Comment 3

[Robert Longson [:longsonr]]

Most likely fixed by bug 767056

Comment 4

[Eddie Maddox]

(In reply to Robert Longson from comment #3)
> Most likely fixed by bug 767056

The Beta/Aurora commits for that bug may have
just missed the Beta builds for last week.

Hangs: SeaMonkey/2.13b2:
User agent: Mozilla/5.0 (X11; Linux i686; rv:16.0)
Gecko/20120906 Firefox/16.0 SeaMonkey/2.13
Build identifier: 20120906034004

Works!:
User agent: Mozilla/5.0 (X11; Linux i686; rv:17.0)
Gecko/17.0 Firefox/17.0 SeaMonkey/2.14a2
Build identifier: 20120911013002

I'll try the next SeaMonkey Beta when available.
Thanks.

Comment 5

[Eddie Maddox]

Works!: SeaMonkey/2.13b3:
User agent: Mozilla/5.0 (X11; Linux i686; rv:16.0)
Gecko/20120912 Firefox/16.0 SeaMonkey/2.13
Build identifier: 20120912212615

Thanks very much for fixing this.
However, does Open Source include methodologies and
Best Practices for making sure bugs
never happen in the First Place ever again?
Eddie Maddox

Comment 6

[Matthias Versen [:Matti]]

>never happen in the First Place ever again?

We have thousands of automated tests that are run after each source code check in.
A change to the source to fix a bug usually includes a new test to be sure that this doesn't happen again.