Bug 9894
| Summary: | www.makro.co.uk hangs (String.replace doesn't work with certain high-bit latin-1 patterns) | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Marcus Bointon <marcus> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | ap, darin, ddkilzer, ian, joost, mitz |
| Priority: | P2 | ||
| Version: | 420+ | ||
| Hardware: | Mac (PowerPC) | ||
| OS: | OS X 10.4 | ||
| URL: | http://www.makro.co.uk/ | ||
Marcus Bointon
http://www.makro.co.uk/ site hangs Safari for me, using either current 419 release or nightly build. I've disabled all plugins, but it still dies. It either dies with a blank page, or after the main page has loaded, but before the pop-up that initially appears has loaded any content. The site works ok in Firefox.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
mitz
I couldn't reproduce a crash, but the page does hang WebKit in an infinite JavaScript loop, caused by the fact that String.replace() behaves strange with the section sign character § (U+00A7): "a§".replace(/§/,"b") gives "a§" instead of "ab".
Marcus Bointon, does the site cause WebKit to crash or just a hang? If it causes a crash, please attach a crash report. Thanks in advance!
Marcus Bointon
No it doesn't crash - I rephrased it as a hang in the body, but forgot to change the title. However, it's as good as a crash in terms of user experience - the only way out is to force quit. Nice to know that you narrowed it down to that cause so quickly!
Joost de Valk (AlthA)
A reproducible hang is arguably just as bad as a crash. Changing to P1, changing subject.
David Kilzer (:ddkilzer)
Adding NeedsRadar since this would probably be a good bug to fix. If it is not, please clear the keyword.
mitz
I don't think P1 and "good to fix" (in that specific context) are warranted. JavaScript hangs are addressed separately, while the String/RegExp bug is not a regression.
mitz
Duplicate of bug 8395?
Joost de Valk (AlthA)
Could very well be, does the patch for that bug solve this problem too?
mitz
Fixed by fixing bug 8395.