thanks for figuring out the problem.

anyhow: my opinion is that Gem is not at fault here. 

Gem uses [FTGL](http://ftgl.sf.net) for font rendering (FTGL in turn uses 
libfreetype to decide the font), and it seems that it is really FTGL that is 
crashing.

doing a quick check with FTGLDemo (2.1.3~rc5) shows that FTGL is indeed 
crashing:
  - start `./FTGLDemo /path/to/Beams.ttf`
  - (rendering seems to work though there are a lot of artefacts)
  - type <kbd>Left</kbd> (*ARROW-LEFT* to decrease font-size)
  - CRASH

alternatively running `./FTGLMFontDemo /path/to/Beams.ttf` immediately crashes.

the problem persists with the current SVN version of FTGL.


---

** [bugs:#220] [text3d] crashes PD if the letter "p" is typed**

**Status:** open
**Created:** Sun Dec 08, 2013 09:22 PM UTC by hellocatfood
**Last Updated:** Mon Dec 30, 2013 04:29 AM UTC
**Owner:** nobody

I'm using PD extednded 0.43.4 and have noticed that when using some fonts 
[text3d] will crash PD when a string with five or more characters is entered.

Font used is Beams: http://openfontlibrary.org/en/font/beams

And the error returned is:

``pd: ../src/libtess/priorityq.c:164: __gl_pqSortInit: Assertion `((((GLUvertex 
*)**(i+1))->s < ((GLUvertex *)**i)->s) || (((GLUvertex *)**(i+1))->s == 
((GLUvertex *)**i)->s && ((GLUvertex *)**(i+1))->t <= ((GLUvertex *)**i)->t))' 
failed.
Pd: signal 6``

I using a Dell XPS 13 developer edition running Ubuntu 13.10 with Intel® 
Ivybridge Mobile graphics and Intel® Core™ i7-3537U CPU @ 2.00GHz × 4 processors

I've attached a patch and the font file for testing



---

Sent from sourceforge.net because [email protected] is subscribed to 
https://sourceforge.net/p/pd-gem/bugs/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/pd-gem/admin/bugs/options.  Or, if this is a mailing 
list, you can unsubscribe from the mailing list.
_______________________________________________
GEM-dev mailing list
[email protected]
http://lists.puredata.info/listinfo/gem-dev

Reply via email to