Bug 12449

Summary:

REPRODUCIBLE HANG: WebKit freezes when printing as PDF a certain kind of code

Product:

WebKit

Reporter:

David Latapie <david>

Component:

Printing

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED FIXED

Severity:

Major

CC:

ddkilzer

Priority:

Keywords:

HasReduction, InRadar

Version:

418.x

Hardware:

Mac (PowerPC)

OS:

OS X 10.4

Attachments:

Description	Flags
Buggy code, will freeze when printing as PDF	none
Clean code, with a ddd in-between the two dt	none
Sample	none

David Latapie

Reported 2007-01-28 09:10:03 PST

Attached is the code. This is a serendituous discovery: I just made a mistake in my code (two dt together with no dd in between). Copy the code below in an editor then print it as PDF with Webkit (419.3, from today) Here is the code ==== <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8" /> <title>L’Italia</title> <style type="text/css"> dl.run-in dt {display:run-in} body {max-width:40em} </style> </head> <body> <dl class="run-in"> <dt>Name</dt> <dt>Surname</dt> <dd>Willis</dd> </dl> </body> </html> ==== With a dd in-between the two dt, no problem.

Attachments
Buggy code, will freeze when printing as PDF (487 bytes, text/html) 2007-01-28 09:13 PST, David Latapie	no flags	Details
Clean code, with a ddd in-between the two dt (504 bytes, text/html) 2007-01-28 09:17 PST, David Latapie	no flags	Details
Sample (15.96 KB, text/plain) 2007-01-28 10:36 PST, Matt Lilek	no flags	Details
View All Add attachment proposed patch, testcase, etc.

David Latapie

Comment 1 2007-01-28 09:13:18 PST

Created attachment 12724 [details] Buggy code, will freeze when printing as PDF

David Latapie

Comment 2 2007-01-28 09:17:19 PST

Created attachment 12725 [details] Clean code, with a ddd in-between the two dt I attached the two testcases. Notice the problem is the same with <meta http-equiv="content-type" content="application/xhtml+xml" /> instead of text/html

Matt Lilek

Comment 3 2007-01-28 10:35:43 PST

Confirmed with Safari 2.0.4 and r19197.

Matt Lilek

Comment 4 2007-01-28 10:36:50 PST

Created attachment 12726 [details] Sample

David Kilzer (:ddkilzer)

Comment 5 2007-01-28 11:32:06 PST

Reproducible hangs are P1.

Mark Rowe (bdash)

Comment 6 2007-01-28 15:34:55 PST

<rdar://problem/4960095>

David Latapie

Comment 7 2007-01-28 16:26:30 PST

(In reply to comment #5) > Reproducible hangs are P1. Thank you, I did not know (In reply to comment #6) > <rdar://problem/4960095> Mark; does it mean that it is already referenced at Apple's bug tracking system, or you are just mentioning where you added it? I'm a bit unfamiliar with the relationships between WebKit and Apple teams of software, hence my question

David Kilzer (:ddkilzer)

Comment 8 2007-01-28 17:30:00 PST

(In reply to comment #7) > (In reply to comment #6) > > <rdar://problem/4960095> > Mark; does it mean that it is already referenced at Apple's bug tracking > system, or you are just mentioning where you added it? I'm a bit unfamiliar > with the relationships between WebKit and Apple teams of software, hence my > question Radar (or "rdar") is Apple's internal bug tracking tool. WebKit is going through a stabilization period now, so any crashes, regressions or hangs need a corresponding Radar bug for them so the Safari/WebKit team knows how much work they have ahead of them. Note that you may file your own Radar bugs using http://bugreport.apple.com/. If you're not an ADC member, you may sign up for a free "Online" ADC account using http://connect.apple.com/.

John Sullivan

Comment 9 2007-02-09 14:15:58 PST

Fixed in r19539. However, there's still an assertion firing downstream, which is indicative of some badness but does not crash or hang on release builds. I'll file a new bug about that.

John Sullivan

Comment 10 2007-02-09 14:50:47 PST

New bug for remaining assertion is 12716.

Note You need to log in before you can comment on or make changes to this bug.