Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 128649 - Eclipse crashes when long line written to the console [font antialiasing is turned off]
Summary: Eclipse crashes when long line written to the console [font antialiasing is t...
Status: RESOLVED DUPLICATE of bug 87299
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.2   Edit
Hardware: Other Linux
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-20 09:43 EST by Michael Kleinhenz CLA
Modified: 2006-04-04 16:33 EDT (History)
3 users (show)

See Also:


Attachments
Image of the brokern font rendering on the console. (58.30 KB, image/jpeg)
2006-02-23 09:25 EST, Michael Kleinhenz CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Kleinhenz CLA 2006-02-20 09:43:18 EST
On 3.2 M5 and prior (tested on 3.1.2), Eclipse crashes when running a large Swing based JDT project and font antialiasing is turned off.

On Kubuntu 5.10, when turning off font antialiasing in the KDE control panel either completely or by specifying a font size range, Eclipse crashes upon start of a large Swing project with:

The program 'Eclipse' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'.
  (Details: serial 51794 error_code 16 request_code 36 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Eclipse 3.1.2 reported no error at all, just crashes. This problem tuns up with different xorg drivers, either ATI proprietary or the free ati/radeon driver.

I tracked it down to the settings in .fonts.conf (see attached file). If the settings for excluding font sizes from antialiasing is commented in, Eclipse crashes.

------------------ .fonts.conf --------------------------
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<!-- UNCOMMENT THIS SECTION TO ENABLE ANTIALIAS FOR BOLD FONTS
<match target="font">
 <test name="weight">
  <const>bold</const>
  <const>black</const>
 </test>
 <edit name="antialias" mode="assign">
  <bool>true</bool>
 </edit>
</match>
--> <match target="pattern" >
  <test name="family" qual="any" >
   <string>Bitstream Vera Sans</string>
  </test>
  <edit mode="assign" name="family" >
   <string>Arial</string>
  </edit>
 </match>
 <match target="pattern" >
  <test name="family" qual="any" >
   <string>Helvetica</string>
  </test>
  <edit mode="assign" name="family" >
   <string>Arial</string>
  </edit>
 </match>
 <match target="pattern" >
  <test name="family" qual="any" >
   <string>Palatino</string>
  </test>
  <edit mode="assign" name="family" >
   <string>Georgia</string>
  </edit>
 </match>
 <match target="font" >
  <edit mode="assign" name="hinting" >
   <bool>true</bool>
  </edit>
 </match>
 <match target="font" >
  <edit mode="assign" name="hintstyle" >
   <const>hintslight</const>
  </edit>
 </match>

<!-- The following two match elements crash eclipse when commented in -->

<!--
 <match target="font" >
  <test compare="more" name="size" qual="any" >
   <double>0</double>
  </test>
  <test compare="less" name="size" qual="any" >
   <double>11</double>
  </test>
  <edit mode="assign" name="antialias" >
   <bool>false</bool>
  </edit>
 </match>
 <match target="font" >
  <test compare="more" name="pixelsize" qual="any" >
   <double>0</double>
  </test>
  <test compare="less" name="pixelsize" qual="any" >
   <double>11</double>
  </test>
  <edit mode="assign" name="antialias" >
   <bool>false</bool>
  </edit>
 </match>
-->

</fontconfig>
------------------ .fonts.conf --------------------------
Comment 1 Billy Biggs CLA 2006-02-21 00:01:58 EST
What version of GTK+, pango, and cairo are installed?

request_code 36 is XGrabServer().
Comment 2 Michael Kleinhenz CLA 2006-02-21 03:26:51 EST
Package: libpango1.0-0
Architecture: i386
Version: 1.10.1-0ubuntu1

Package: libgtk2.0-0
Architecture: i386
Version: 2.8.6-0ubuntu2.1

Package: libcairo2
Architecture: i386
Version: 1.0.2-0ubuntu1

I forgot to mention that when Eclipse crashes, the started swing application starts without any problems. It seems that the crash occures just when the main window of it opens. In the end, I'll get the application running and the eclipse crash notification window.
Comment 3 Michael Kleinhenz CLA 2006-02-23 09:25:48 EST
Created attachment 35230 [details]
Image of the brokern font rendering on the console.

This shows the output of a very long line of text in the console view. If font rendering is turned off, this crashes Eclipse. Even with antialiasing on, it crashes sometimes.
Comment 4 Michael Kleinhenz CLA 2006-02-23 09:29:51 EST
I looked into this problem again. It seems that the crash is not caused by the
swing app directly, but from the debugging output on the console (or other
views).

If the client application prints a very long line on the console, it seems, the
text "folds" and overwrites itself, causing a weird, unreadable font display. 

I attached an image of the problem to this bug.

If antialiasing is turned off, Eclipse crashes the moment this line is printed.
Even with antialiasing, it crashes sometimes. 

The problem not only shows up in the console, but also in other views. If I
inspect a variable with a very long string, the text is equally broken rendered
in the inspection view of the debugging perspective, causing Eclipse to crash.
Comment 5 Steve Northover CLA 2006-04-04 12:16:34 EDT
There was a Windows driver bug that was the same as this that we marked WONTFIX.  Could this be a Linux manifestation of the same problem?
Comment 6 Billy Biggs CLA 2006-04-04 16:33:31 EDT
This is what happens when you blow the limit for pango pixels
or for the X window size limit.  Not really related to font
antialiasing, although you can hit the limits in different ways.

Our choice is either to try and determine the limits and just clip
strings (nasty), or let the application set reasonable limits
before setting the text in the underlying widgets.  For example,
the console view has a limit you can set on the width of lines.

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