Bug 71289 - Crash in PDF code when script has illegal UTF-8 or UTF-16 sequences
Summary: Crash in PDF code when script has illegal UTF-8 or UTF-16 sequences
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: PDF (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Darin Adler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-01 09:12 PDT by Darin Adler
Modified: 2011-11-01 10:46 PDT (History)
1 user (show)

See Also:


Attachments
Patch (1.92 KB, patch)
2011-11-01 09:13 PDT, Darin Adler
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Adler 2011-11-01 09:12:06 PDT
Crash in PDF code when script has illegal UTF-8 or UTF-16 sequences
Comment 1 Darin Adler 2011-11-01 09:13:22 PDT
Created attachment 113175 [details]
Patch
Comment 2 Darin Adler 2011-11-01 09:28:21 PDT
Comment on attachment 113175 [details]
Patch

Clearing flags on attachment: 113175

Committed r98970: <http://trac.webkit.org/changeset/98970>
Comment 3 Darin Adler 2011-11-01 09:28:24 PDT
All reviewed patches have been landed.  Closing bug.
Comment 4 Alexey Proskuryakov 2011-11-01 09:56:53 PDT
Is it correct to only support UTF-8 and UTF-16 with BOM? Where should the encoding information come from?
Comment 5 Darin Adler 2011-11-01 10:46:31 PDT
(In reply to comment #4)
> Is it correct to only support UTF-8 and UTF-16 with BOM? Where should the encoding information come from?

That’s a good question, and it occurred to me too. But far, far less important than this bug.