Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Mavericks is the buggiest POS OS since 7.5.2
#1
With apologies to 7.5.2 if previous systems were buggier, it was my first.


Still getting sudden system freezes (crashes) with cursor/display freeze.
Typically happens when browsing a news site or in the case a few minutes ago a Facebook page in hebrew linked in another thread. I go to scroll and 'blam'-- frozen.
I followed the advice in the previous thread to delete duplicate fonts-- have no idea what I got rid of or exactly why, but it was a lot.
"Fresh" error log:

4/23/14 6:37:47.933 PM plugin-container[8738]: CoreText performance note: Client called CTFontCreateWithName() using name "Times Roman" and got font with PostScript name "Times-Roman". For best performance, only use PostScript names when calling this API.
4/23/14 6:37:47.934 PM plugin-container[8738]: CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.
4/23/14 6:39:00.000 PM bootlog[0]: BOOT_TIME 1398296340 0
Reply
#2
Maybe that console message doesn't relate to the freeze.
I got the same one just now when I went back to the page that caused the freeze (absolutely no problem this time.)

4/23/14 6:47:50.074 PM plugin-container[479]: CoreText performance note: Client called CTFontCreateWithName() using name "Times Roman" and got font with PostScript name "Times-Roman". For best performance, only use PostScript names when calling this API.
4/23/14 6:47:50.074 PM plugin-container[479]: CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.
Reply
#3
Get rid of the hyphen in 'Times-Roman'.

I loved System 7.5. Power PC and flashy as can be on my PowerMac 6115CD.
Reply
#4
Corrupted font(s)?

http://macnancy.wordpress.com/2013/05/14...ith-fonts/
Reply
#5
Black wrote:
With apologies to 7.5.2 if previous systems were buggier...

I made that same comparison today.

No... Wait... That was 10.7.2.

10.9.2 is as buggy as 10.7.2.

...

Probably not related to your crashes, but if you're having font problems they're probably easy to deal with.

Run the Font Book app, select the library from the left panel; type command+a to select all fonts; control-click on a highlighted font and select "resolve duplicates" from the contextual menu. If no duplicates are found then control-click and select "validate fonts." In the resulting window, opt to show only fonts with errors and delete those fonts that have errors.
Reply
#6
:hail:

Chakravartin wrote:
Probably not related to your crashes, but if you're having font problems they're probably easy to deal with.

Run the Font Book app, select the library from the left panel; type command+a to select all fonts; control-click on a highlighted font and select "resolve duplicates" from the contextual menu. If no duplicates are found then control-click and select "validate fonts." In the resulting window, opt to show only fonts with errors and delete those fonts that have errors.
Reply
#7
How can a bad font crash a UNIX operating system?
Reply
#8
And how much did you pay for it? Confusedympathy:
Reply
#9
Chakravartin wrote:
[quote=Black]
With apologies to 7.5.2 if previous systems were buggier...

I made that same comparison today.

No... Wait... That was 10.7.2.

10.9.2 is as buggy as 10.7.2.

...

Probably not related to your crashes, but if you're having font problems they're probably easy to deal with.

Run the Font Book app, select the library from the left panel; type command+a to select all fonts; control-click on a highlighted font and select "resolve duplicates" from the contextual menu. If no duplicates are found then control-click and select "validate fonts." In the resulting window, opt to show only fonts with errors and delete those fonts that have errors.
Read above. I followed this advice and thought I was all good, but nope.
Reply
#10
Filliam H. Muffman wrote:
And how much did you pay for it? Confusedympathy:

$759 plus tax.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)