hilarious!!! fontlab errors

Santiago Orozco's picture
Ray Larabie's picture

That what it sounds like inside my head.

Mark Simonson's picture

Maybe I'm doing it wrong, but it doesn't crash/error all that often for me.

Thomas Phinney's picture

Mark: Are you using Mac or Windows?

Popular wisdom seems to suggest the Mac version is much less stable than the Windows version. I run FL for Windows for any serious work, even if it means doing it under a VM on Mac.


Igor Freiberger's picture

I must be doing something wrong too... FonLab never crashed to me (running under Windows Vista 64-bit). :-)

Seriously, I have a clean, perfect complete system installation in an image (created with TrueImage). About each two months I do a complete system reinstall using this image. It take about 15 minutes and keeps Windows under control. This may be the reason FontLab in running OK with me.

Mark Simonson's picture

I'm on a Mac (10.6.4). Maybe I'm just lucky.

Nick Shinn's picture

I'm with Mark, on Mac.
Sure it crashes occasionally, but I've been working with it long enough I have a feeling for avoiding that.
So I never drag a guide onto a glyph composed of composites, for instance.

.00's picture

FL always has the good graces to freeze after I've stopped working and switched to another app.

Very little trouble these days, perhaps those messages are from users of FL 4.6, now that was a bundle o' bugs.

eliason's picture

There's also a Flickr pool dedicated to the topic.

I'm on a Mac (10.5.8) and I get FontLab (5.0.4) crashes and errors more than any other non-beta applications I can remember using.

dezcom's picture

"So I never drag a guide onto a glyph composed of composites, for instance."

Pre-intel Mac as well 10.4.11. FL5 has occasional freak-outs. SAVE OFTEN! FontLab is one of the rare apps that give me the spinning beach ball. The only worse ones are anything in the Microsoft suite. Otherwise, my Mac is as steady and solid as can be.

and I never switch between kinds of classes via the pop-up. Also, if you get a bunch of random diagonal lines drawn courtesy of FontLab demons, undo twice and relaunch FontLab.


Nick Shinn's picture

The worst bug I ever experienced was in a version of Quark, where if you moved your cursor just a lit little bit off the top of a pull-down menu, you got the bomb. Remember the bomb? -- compared to which the spinning beach ball is a smarmy euphemism.

dezcom's picture

The pre OSX bomb looked like something from Acme of RoadRunner cartoon fame, complete with lit fuse :-)
OSX is WAY more stable than its predecessor.

Santiago Orozco's picture

I think FL knows who the big guys are and plays with the newbies!

but really think there's something with phyton scripts and some environment variables on OSX that provoke this.

Ray Larabie's picture

I use Windows 7 and I still manage to crash thrice a week. I recently had to do a fresh OS install and it crashes at the same frequency. It depends what I'm working on. If I'm arrow key tapping points, it's unlikely to crash. If I'm messing with the mask layer, composites, paste special, classes or dragging and dropping glyphs, I'm more likely to crash it. The current version of FLS doesn't crash as predictably as older versions did. I used to have to do certain things to avoid crashes. But now it's different. I can do something to make it crash, load the same font, do exactly the same thing again and it won't crash.

Syndicate content Syndicate content