Bug 13266 - "Fatal IO error 104" when font size is too large
Summary: "Fatal IO error 104" when font size is too large
Status: RESOLVED DUPLICATE of bug 4339
Alias: None
Product: cairo
Classification: Unclassified
Component: general (show other bugs)
Version: 1.4.10
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Carl Worth
QA Contact: cairo-bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-15 23:06 UTC by Jake Brownson
Modified: 2008-04-04 09:11 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Simple demonstration of the problem (831 bytes, text/x-csrc)
2007-11-15 23:08 UTC, Jake Brownson
Details

Description Jake Brownson 2007-11-15 23:06:58 UTC
When the font size is set large relative to the display and show_text is used the program crashes with the following message:

Fatal IO error 104 (Connection reset by peer) on X server :0.0.

I specifically noticed this as I have a habbit of scaling my cairo windows to be 1x1 and the default font size was large enough to cause this. Attached is an example program to recreate the crash.

The font size that makes things crash seems to be dependant on the font selection, but is difficult to narrow down exactly.

I'll attach a simple example to reproduce the problem.
Comment 1 Jake Brownson 2007-11-15 23:08:34 UTC
Created attachment 12583 [details]
Simple demonstration of the problem
Comment 2 Behdad Esfahbod 2007-11-16 10:38:53 UTC
What's the window size?  This is probably the glyph image exceeding X max request size which is 32k IIRC.
Comment 3 Jake Brownson 2007-11-16 10:54:47 UTC
The default window size seems to be 200x200.

Maybe Cairo could check the size before requesting it to make sure it will work, and give a nice error if not, or is X doing an error code that Cairo just isn't handling well?
Comment 4 Steve Chaplin 2007-11-16 16:25:56 UTC
This looks like a duplicate of bug #4339.
Comment 5 Jake Brownson 2007-11-16 16:30:57 UTC
I think you're right
Comment 6 Chris Wilson 2008-04-04 09:11:25 UTC

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


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.