Bug 14446 - [GDK] Crash on http://www.wikipedia.org/
Summary: [GDK] Crash on http://www.wikipedia.org/
Status: RESOLVED DUPLICATE of bug 16054
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 523.x (Safari 3)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL: http://www.wikipedia.org/
Keywords: Gtk
Depends on:
Reported: 2007-06-28 08:56 PDT by Alp Toker
Modified: 2007-11-19 17:57 PST (History)
0 users

See Also:

backtrace of crash from recent webkit (8.57 KB, text/plain)
2007-10-22 02:19 PDT, Jan Alonzo
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alp Toker 2007-06-28 08:56:41 PDT
The test browser crashes when loading http://www.wikipedia.org/

I suspect this has to do with complex text support.
Comment 1 Jan Alonzo 2007-10-22 02:19:48 PDT
Created attachment 16787 [details]
backtrace of crash from recent webkit

Attached is a backtrace of the crash from recent webkit
Comment 2 Andres Gomez Garcia 2007-10-25 11:03:17 PDT
It seems it crashes when calling to the delete standard C++ function. This is a weird error since, tracking the problem, we have downloaded the Wikipedia home page to the local harddisk.

Opening the page with:

The page renders perfectly with no errors.

We've uploaded the same Wikipedia.html (without images) to another webserver and the page keeps crashing. Also, it keeps crashing without having the images available.

We have made some more tests: removing the javascript code -> it keeps crashing, trying to remove the problematic text in the page -> there is no problematic text, since when you remove some amount of content, the page doesn't crashes anymore but, adding the removed text and removing the kept text leads to a non crashing page too.

Debugging the page while loading: as shown in the page, it crashes when calling 
#44 0xb78346cf in WebCore::GlyphPageTreeNode::initializePage (this=0x83e8560, fontData=0x813c528, pageNumber=259) at ../../../WebCore/platform/GlyphPageTreeNode.cpp:150 when trying to defer the GlyphPage object.

When loading the page locally, we don't call WebCore::GlyphPageTreeNode::initializePage with pageNumber set to 259 ever.

It seems a quite weird problem and, since it doesn't happen locally nor with the Qt port, we think the problem could be in the used network backend in GTK+ port -> libcurl.
Comment 3 Alp Toker 2007-10-25 23:12:23 PDT
Thanks for the sleuth worth so far. To make things more interesting, wikipedia.com does not crash when I use Pango for text rendering instead of the old code path. (Pango patch is not yet released.)

Pango won't be the default font engine so this bug still matters.
Comment 4 Alp Toker 2007-11-13 00:12:51 PST
Preliminary Pango patch released in an attachment to #15610

wikipedia.com loads with that patch applied. It uses Pango for all text though, which is not what we want by default.
Comment 5 Alp Toker 2007-11-19 17:57:05 PST

*** This bug has been marked as a duplicate of 16054 ***