http://bugs.winehq.org/show_bug.cgi?id=17338
--- Comment #13 from Tim Mertens tim@filmchicago.org 2009-02-12 22:55:48 --- Additionally, digging a little more in the log I noticed another oddity:
"trace:font:WineEngGetTextExtentExPoint 0x3338e10, L"Feb 2009", 8, 0, 0x3241cc trace:font:WineEngGetGlyphOutline 0x3338e10, 002b, 00000080, 0x323f58, 00000000, (nil), (nil) trace:font:WineEngGetGlyphOutline font transform 1.000000 0.000000 0.000000 1.000000 trace:font:WineEngGetGlyphOutline Vec 64,768 trace:font:WineEngGetGlyphOutline Vec 64,0 trace:font:WineEngGetGlyphOutline Vec 576,768 trace:font:WineEngGetGlyphOutline Vec 576,0"
This area just before the hang is the only point in the log where the line "WineEngGetGlyphOutline font transform 1.000000 0.000000 0.000000 1.000000" is followed by the four lines of: "trace:font:WineEngGetGlyphOutline Vec $x,$y" This appears several times before it actually tries to execute UploadGlyph.
Normally, it looks like this: "trace:font:WineEngGetGlyphOutline font transform 1.000000 0.000000 0.000000 1.000000 trace:font:WineEngGetGlyphOutline 1,10,(1,10),3,0"
So the question to ask is why does WineEngGetGlyphOutline have a problem in this particular instance and not in the rest of the log?