See zipped up testcase, to reproduce: - Extract the contents of the zipped up testcase - Open "Kopie (3) van parentframe2.htm" and accept the request for enhanced privileges Let this run for a while, it's causing this crash within appr. 5 minutes. The testcase reflects highly of what fonts I've installed on my system, I guess that might affect the crashiness on other computers. Otherwise just open the "Kopie (3) van parentframe2.htm" file in 2 tabs, that should quicken the crash. You can watch the amount of GDI objects that Firefox is using in the task manager. When it reaches 10000, Firefox can crash, or you see text in the chrome disappearing or just hang. http://crash-stats.mozilla.com/report/index/050b4da6-0b03-11dd-b5d3-001cc4e2bf68 0 xul.dll UniscribeItem::IsGlyphMissing mozilla/gfx/thebes/src/gfxWindowsFonts.cpp:1267 1 xul.dll xul.dll@0x26e2dd
For people who might wonder where the zipped up testcase is, I attached it as a private attachment, because of secret reasons.
Still happening in current trunk build: http://crash-stats.mozilla.com/report/index/b05d5091-19bc-11dd-9329-001a4bd46e84?p=1
Another effect that can happen when the amount of 10000 GDI objects is reached, is that text in the chrome is not showing up anymore, like described in bug 443939. See screenshot in that bug: http://img503.imageshack.us/my.php?image=ffbugzh6.png
Hey Martijn, could we possible dupe this to bug 445385, "random crashes, gdi resource starvation"? The stacks look different, but gdi resource starvation seems to be a common theme between both.
Fine by me. I think last time I checked this, it was actually wfm, but not sure.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 445385
Never mind, this still seems to be crashing. The crash reporter isn't able to send a crash report.
Crash Signature: [@ UniscribeItem::IsGlyphMissing]
You need to log in before you can comment on or make changes to this bug.