Last modified: 2012-11-29 21:47:29 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T35100, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 33100 - WebFonts crashes Chrome on OSX
WebFonts crashes Chrome on OSX
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
WebFonts (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://ne.wikipedia.org/wiki/%E0%A4%A...
: i18n, upstream
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-12-14 12:40 UTC by Siebrand Mazeland
Modified: 2012-11-29 21:47 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Siebrand Mazeland 2011-12-14 12:40:34 UTC
Taken out of bug 33039 comment 3.

On page http://ne.wikipedia.org/wiki/%E0%A4%A8%E0%A5%87%E0%A4%AA%E0%A4%BE%E0%A4%B2, Google Crome on OSX 10.7.2 crashes. Also reported for Mac OS X 10.7.2 (11C74) with Safari 5.1.1 (7534.51.22, r102522)  [This is a
webkit nightly build] by thedj.

This is most probably related to the WebFonts code, because if, as a logged in user I disable web fonts in preferences, the page does not crash Chrome.
Comment 1 Siebrand Mazeland 2011-12-14 12:43:50 UTC
Derk-Jan, can you please report this issue with WebKit, and add a URL to the report here?
Comment 2 Antoine "hashar" Musso (WMF) 2012-01-30 21:30:49 UTC
I do not have the issue on Mac OS X 10.7.2, Safari 5.1.2 (7534.52.7)
Comment 3 Antoine "hashar" Musso (WMF) 2012-01-30 22:30:38 UTC
Taking this bug to try to reproduce it since I own a Mac OS X system.
Comment 4 Siebrand Mazeland 2012-01-30 22:44:47 UTC
(In reply to comment #2)
> I do not have the issue on Mac OS X 10.7.2, Safari 5.1.2 (7534.52.7)

Comment 2 confirmed.

All OSX 10.7.2 (11C74) and anonymous user:

* Safari Version 5.1.2 (7534.52.7): OK
* Firefox 9.0.1: OK
* Opera 11.61 build 1205: OK

* Chrome 16.0.912.77: Not OK. Crash of tab
Comment 5 Siebrand Mazeland 2012-01-30 23:05:23 UTC
Tested beta and alpha versions:

All OSX 10.7.2 (11C74) and anonymous user:

* Chrome 17.0.963.46 beta: Not OK. Crash of tab
* Chrome 18.0.1017.2 dev: Not OK. Crash of tab

Reported upstream: http://code.google.com/p/chromium/issues/detail?id=112007

It would probably be a good idea if someone can add a second crash id and client id in that issue.
Comment 6 Antoine "hashar" Musso (WMF) 2012-01-31 10:17:08 UTC
I have tried again using the latest buid at the moment 18.0.1024.0 - 119801 (fetched from the continuous build system http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html ).

I have copy pasted the article to a user subpage and then blanked up part of the article content. The browser kept crashing.  Eventually it stopped crashing at some point.

Comment added to upstream bug report:
http://code.google.com/p/chromium/issues/detail?id=112007#c1
Comment 7 Antoine "hashar" Musso (WMF) 2012-01-31 11:05:50 UTC
Issue reproduced with WebKit-SVN-r106324
#chromium people instructed me to also a bug report for the WebKit engine.

https://bugs.webkit.org/show_bug.cgi?id=77418
Comment 8 Siebrand Mazeland 2012-01-31 11:32:43 UTC
Okay. Guess we're done here for now, then, unless there's a (very small?) particular content part we can identify causing the crash?
Comment 9 Antoine "hashar" Musso (WMF) 2012-01-31 20:17:13 UTC
The bug was added to Apple internal bug tracker (issue <rdar://problem/10701562> , unaccessible to non Apple people)
Comment 10 Rob Lanphier 2012-02-02 00:26:53 UTC
Bumping to low priority while waiting response from WebKit devs.
Comment 11 Siebrand Mazeland 2012-11-29 21:47:29 UTC
Upstreams have closed this issue. Solution is to update to OSX 10.8.x, as the issue apparently originated from OSX.

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


Navigation
Links