Bug 90435 - [CSS Regions] Enabling regions on Windows lead to crash-on-launch for WebKit.exe
Summary: [CSS Regions] Enabling regions on Windows lead to crash-on-launch for WebKit.exe
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Windows 7
: P2 Normal
Assignee: Nobody
URL:
Keywords:
: 89430 (view as bug list)
Depends on:
Blocks: 57312
  Show dependency treegraph
 
Reported: 2012-07-03 00:19 PDT by Mihai Balan
Modified: 2012-11-22 00:08 PST (History)
2 users (show)

See Also:


Attachments
Moved getter/setter for css regions in IWebPreferences.idl at the end of the file fixes the crash (1.98 KB, patch)
2012-07-03 00:42 PDT, Mihai Balan
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Mihai Balan 2012-07-03 00:19:29 PDT
After fixing #88645 WebKit.exe started crashing upon launch.

Upon further investigation the problem was in IWebPreferences.idl, where the setter/getter for css regions was added in the middle of the interface and not at the end. (A similar thing happened here http://trac.webkit.org/changeset/95650 )
Comment 1 Mihai Balan 2012-07-03 00:42:29 PDT
Created attachment 150552 [details]
Moved getter/setter for css regions in IWebPreferences.idl at the end of the file fixes the crash
Comment 2 Csaba Osztrogonác 2012-07-03 02:08:45 PDT
Comment on attachment 150552 [details]
Moved getter/setter for css regions in IWebPreferences.idl at the end of the file fixes the crash

rs=me
Comment 3 WebKit Review Bot 2012-07-03 03:25:52 PDT
Comment on attachment 150552 [details]
Moved getter/setter for css regions in IWebPreferences.idl at the end of the file fixes the crash

Clearing flags on attachment: 150552

Committed r121755: <http://trac.webkit.org/changeset/121755>
Comment 4 WebKit Review Bot 2012-07-03 03:25:57 PDT
All reviewed patches have been landed.  Closing bug.
Comment 5 Mihai Balan 2012-11-22 00:08:06 PST
*** Bug 89430 has been marked as a duplicate of this bug. ***