Anyone else with crash problems?

[AlanBDahl]

When I first upgraded to Snow Leopard OW crashed all the time with a Font error but deleting everything from ~/Library/Fonts solved the problem. However after the latest 10.6.2 update the crashing problem has returned even though ~/Library/Fonts is empty. What's really weird is that some websites display fine if I have only one window open and don't navigate to them while if I click a link to get there or open a new window when I have an existing window open to another site, bam it crashes right away. What's frustrating is that two of the sites I'm having problems with are YouTube and eBay. Has anybody else seen something similar?

I'm working with the support ninjas at Omni to resolve it but this one's taking a long time and it's frustrating to have to deal with the crashes or switch to Safari to view certain sites. Any suggestions would be most appreciated!

[AlanBDahl]

Is OmniWeb crashing all the time under Snow Leopard for anyone else? It's getting quite frustrating and I'm sure the Omni folks are excited about getting so many crash reports per day, sigh.

[troyb]

We don't know of any crashers specific to Snow Leopard. Can you tell us some more about what you're doing leading up to the crash?

[rsd22]

Yes, my macbook pro (that I just updated to snow lep) crashes quite frequently - but mostly after I close the laptop, walk away for a few hours, and reopen. That said, I LOVE Omniweb and wish I heard of this product a year ago when I bought my new mac. A crash here and there is not horrible -- though it is a pain since firefox never crashed. I do not use safari.

[hhm]

Is OmniWeb crashing all the time under Snow Leopard for anyone else?
Yes, I am. Even starting a different application is enough for OW to crash. I went back a few versions but that did not make anything better.

(Un-)funny: I tried to write this answer and it crashed.

Slightly annoyed,
Hans

[AlanBDahl]

It seems to be font-related somehow, perhaps because OmniWeb is using an obsolete and deprecated method, CGContextSetFontRenderingMode instead of CGContextSetFontRenderingStyle.

When I first upgraded to Snow Leopard I had this problem but clearing the old fonts out of ~/Library/Fonts fixed it. However since the 10.6.2 update I've been having the same problem even though ~/Library/Fonts is empty. What's odd is that some pages will crash if used in combination with each other but work ok by themselves. However any embedded YouTube page will crash OW instantly and until now I never realized just how common YouTube embedding is.

Creating a new user solves the problem which means it could be either a problem with preferences (though deleting the OW pref folder and pslist don't help) or more likely an issue with an interaction with something installed by another application. If you have crash problems can you let me know if you have Parallels Desktop installed?

This extremely frustrating for me as I've been using OW since 1994 (on a NeXT) and it's become useless with Snow Leopard. So far I've been living with the crashes but if it doesn't get fixed soon I'll have to migrate to Safari :-(.

[whpalmer4]

It seems to be font-related somehow, perhaps because OmniWeb is using an obsolete and deprecated method, CGContextSetFontRenderingMode instead of CGContextSetFontRenderingStyle.
I'm told that it's actually WebKit making that call, not OmniWeb.

In any case, count me among the crowd having little or no trouble with OmniWeb on 10.6.2. If you've got a frequent crasher, cc omniweb@omnigroup.com the next time you send in a crash report to make sure a human looks at it.

[AlanBDahl]

On a whim I tried turning off the Flash player plugin and my crashing problem went away. I tried reinstalling the latest version of Flash for Snow Leopard and that didn't help but there is definitely something funky going on. Since I have been using OmniWeb for so long is it possible that I have some old preference or plugin somewhere that could be causing this problem with Flash?

[LCPGUY]

On a whim I tried turning off the Flash player plugin and my crashing problem went away. I tried reinstalling the latest version of Flash for Snow Leopard and that didn't help but there is definitely something funky going on. Since I have been using OmniWeb for so long is it possible that I have some old preference or plugin somewhere that could be causing this problem with Flash?

I have constant problems with OW and Flash for over a year. Frequent crashes. Since I recently installed the beta version of Flash 10.1, I haven't had a crash yet.

[AlanBDahl]

Removing Flash and reinstalling the new 10.1 version made no difference, it still crashes with an apparent font-related error. As an experiment I'll leave Flash turned off permanently and see if I get any crashes. I'm beginning to think that Flash isn't the culprit but it would not surprise me to learn that it uses whatever uncommon font or webkit font rendering code that's causing the crash.

Besides that I don't know what else I can do. Any other suggestions?

[LCPGUY]

Removing Flash and reinstalling the new 10.1 version made no difference, it still crashes with an apparent font-related error. As an experiment I'll leave Flash turned off permanently and see if I get any crashes. I'm beginning to think that Flash isn't the culprit but it would not surprise me to learn that it uses whatever uncommon font or webkit font rendering code that's causing the crash.

Besides that I don't know what else I can do. Any other suggestions?

Sorry but I can't offer anymore suggestions as this latest build of OW is extremely stable for me. It has "never" crashed.

[troyb]

Alan: I do not think your crash is related to Flash either. The only thing I can think is that perhaps it being loaded into a page is kicking off the events that do cause the crash.

When you experience this problem, do you have a lot of tabs open? Any tabs in the background that are updating even when you're not looking at them perhaps? I'm wondering if there's a particular page you have open that's causing this to occur.

[whpalmer4]

Alan, what is this apparent font-related crash you are seeing (stack trace)? Did you directly contact Omni support as I suggested in another thread?

Have you tried erasing your font caches, and verifying all of your installed fonts with Font Book? Do you have any specific pages that will crash on demand?

[troyb]

I personally cheated and found his crash in our database. If interested, this is the problem we're dealing with here:


Thread 0 Crashed:
0 -- 0x000000b4 -- start
1 -- 0x3456d29e -- __ZNK7WebCore4Font12isFixedPitchEv
2 -- 0x349bbf49 -- __ZN7WebCore11RenderBlock17findNextLineBreakERNS_1 2BidiResolverINS_14InlineIteratorENS_7BidiRunEEEbR bS6_PNS_6EClearE
3 -- 0x349be8ee -- __ZN7WebCore11RenderBlock20layoutInlineChildrenEbR iS1_
4 -- 0x3482069f -- __ZN7WebCore11RenderBlock11layoutBlockEb
5 -- 0x3480fb28 -- __ZN7WebCore11RenderBlock6layoutEv
6 -- 0x3482013f -- __ZN7WebCore11RenderBlock19layoutBlockChildrenEbRi
7 -- 0x34820b99 -- __ZN7WebCore11RenderBlock11layoutBlockEb
8 -- 0x34894836 -- __ZN7WebCore27RenderTextControlSingleLine6layoutEv
9 -- 0x349be43e -- __ZN7WebCore11RenderBlock20layoutInlineChildrenEbR iS1_
10 -- 0x3482069f -- __ZN7WebCore11RenderBlock11layoutBlockEb
11 -- 0x3480fb28 -- __ZN7WebCore11RenderBlock6layoutEv
12 -- 0x349be43e -- __ZN7WebCore11RenderBlock20layoutInlineChildrenEbR iS1_
13 -- 0x3482069f -- __ZN7WebCore11RenderBlock11layoutBlockEb
14 -- 0x3480fb28 -- __ZN7WebCore11RenderBlock6layoutEv
15 -- 0x3482013f -- __ZN7WebCore11RenderBlock19layoutBlockChildrenEbRi
16 -- 0x34820b99 -- __ZN7WebCore11RenderBlock11layoutBlockEb
17 -- 0x3480fb28 -- __ZN7WebCore11RenderBlock6layoutEv
18 -- 0x349be43e -- __ZN7WebCore11RenderBlock20layoutInlineChildrenEbR iS1_
19 -- 0x3482069f -- __ZN7WebCore11RenderBlock11layoutBlockEb
20 -- 0x348831d9 -- __ZN7WebCore15RenderTableCell6layoutEv
21 -- 0x34886fae -- __ZN7WebCore14RenderTableRow6layoutEv
22 -- 0x348898e1 -- __ZN7WebCore18RenderTableSection6layoutEv
23 -- 0x34882354 -- __ZN7WebCore11RenderTable6layoutEv
24 -- 0x3482013f -- __ZN7WebCore11RenderBlock19layoutBlockChildrenEbRi
25 -- 0x34820b99 -- __ZN7WebCore11RenderBlock11layoutBlockEb
26 -- 0x348831d9 -- __ZN7WebCore15RenderTableCell6layoutEv
27 -- 0x34886fae -- __ZN7WebCore14RenderTableRow6layoutEv
28 -- 0x348898e1 -- __ZN7WebCore18RenderTableSection6layoutEv
29 -- 0x34882354 -- __ZN7WebCore11RenderTable6layoutEv
30 -- 0x3482013f -- __ZN7WebCore11RenderBlock19layoutBlockChildrenEbRi
31 -- 0x34820b99 -- __ZN7WebCore11RenderBlock11layoutBlockEb
32 -- 0x3480fb28 -- __ZN7WebCore11RenderBlock6layoutEv
33 -- 0x3482013f -- __ZN7WebCore11RenderBlock19layoutBlockChildrenEbRi
34 -- 0x34820b99 -- __ZN7WebCore11RenderBlock11layoutBlockEb
35 -- 0x348831d9 -- __ZN7WebCore15RenderTableCell6layoutEv
36 -- 0x34886fae -- __ZN7WebCore14RenderTableRow6layoutEv
37 -- 0x348898e1 -- __ZN7WebCore18RenderTableSection6layoutEv
38 -- 0x34882354 -- __ZN7WebCore11RenderTable6layoutEv
39 -- 0x3482013f -- __ZN7WebCore11RenderBlock19layoutBlockChildrenEbRi
40 -- 0x34820b99 -- __ZN7WebCore11RenderBlock11layoutBlockEb
41 -- 0x3480fb28 -- __ZN7WebCore11RenderBlock6layoutEv
42 -- 0x3482013f -- __ZN7WebCore11RenderBlock19layoutBlockChildrenEbRi
43 -- 0x34820b99 -- __ZN7WebCore11RenderBlock11layoutBlockEb
44 -- 0x3480fb28 -- __ZN7WebCore11RenderBlock6layoutEv
45 -- 0x3482013f -- __ZN7WebCore11RenderBlock19layoutBlockChildrenEbRi
46 -- 0x34820b99 -- __ZN7WebCore11RenderBlock11layoutBlockEb
47 -- 0x3480fb28 -- __ZN7WebCore11RenderBlock6layoutEv
48 -- 0x348a910b -- __ZN7WebCore10RenderView6layoutEv
49 -- 0x345a3414 -- __ZN7WebCore9FrameView6layoutEb
50 -- 0x34b62224 -- _sqlite3RunVacuum
51 -- 0x3496bffc -- __ZN7WebCore12ThreadTimers10fireTimersEdRKN3WTF6Ve ctorIPNS_9TimerBaseELm0EEE
52 -- 0x3496c1d8 -- __ZN7WebCore12ThreadTimers24sharedTimerFiredIntern alEv
53 -- 0x3496c23e -- __ZN7WebCore12ThreadTimers16sharedTimerFiredEv
54 -- 0x3494dca1 -- __ZN7WebCore10timerFiredEP16__CFRunLoopTimerPv
55 -- 0x9642eedb -- ___CFRunLoopRun
56 -- 0x9642c864 -- _CFRunLoopRunSpecific
57 -- 0x9642c691 -- _CFRunLoopRunInMode
58 -- 0x91878f0c -- _RunCurrentEventLoopInMode
59 -- 0x91878bff -- _ReceiveNextEventCommon
60 -- 0x91878b48 -- _BlockUntilNextEventMatchingListInMode
61 -- 0x927ceac5 -- __DPSNextEvent
62 -- 0x927ce306 -- -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
63 -- 0x0027bc3e -- -[OAAppKitQueueProcessor shouldProcessQueueEnd]
64 -- 0x003cddef -- -[OFQueueProcessor processQueueUntilEmpty:forTime:]
65 -- 0x0038759d -- -[OFQueueProcessor processQueueUntilEmpty:]
66 -- 0x003875cd -- -[OFQueueProcessor processQueueUntilEmpty]
67 -- 0x003876ee -- -[OFRunLoopQueueProcessor processQueueUntilEmpty]
68 -- 0x91503ff1 -- ___NSFireMachPort
69 -- 0x96432b72 -- ___CFMachPortPerform
70 -- 0x9642e8db -- ___CFRunLoopRun
71 -- 0x9642c864 -- _CFRunLoopRunSpecific
72 -- 0x9642c691 -- _CFRunLoopRunInMode
73 -- 0x91878f0c -- _RunCurrentEventLoopInMode
74 -- 0x91878cc3 -- _ReceiveNextEventCommon
75 -- 0x91878b48 -- _BlockUntilNextEventMatchingListInMode
76 -- 0x927ceac5 -- __DPSNextEvent
77 -- 0x927ce306 -- -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
78 -- 0x9279049f -- -[NSApplication run]
79 -- 0x00278867 -- -[OAApplication run]
80 -- 0x92788535 -- _NSApplicationMain
81 -- 0x0000f61f -- _main
82 -- 0x000027d2 -- __start
83 -- 0x000026f9 -- start

[troyb]

The crash itself appears to have something to do with Webcore setting font attributes. There are a few different variants of this.

[AlanBDahl]

FYI I still get the occasional crash even with Flash turned off. I've also tried the new build of Flash released 12/10 and that made no difference either.

[AlanBDahl]

Alan, what is this apparent font-related crash you are seeing (stack trace)? Did you directly contact Omni support as I suggested in another thread?

Have you tried erasing your font caches, and verifying all of your installed fonts with Font Book? Do you have any specific pages that will crash on demand?

Font caches have been erased, prefs deleted, Macromedia Font cache deleted and I've resolved my duplicate Fonts with Font Book all to no effect. I have not however tried doing all of those at one time. I've also not tried doing a reinstall of Snow Leopard which I suppose might help if for example I have a missing font or something. I doubt that the problem is with the OS however as any new user I create doesn't have the problem, at least not with light testing.

I've been in contact with one of the OW support ninjas (David M) but haven't heard any new suggestions since Monday morning.

[AlanBDahl]

When you experience this problem, do you have a lot of tabs open? Any tabs in the background that are updating even when you're not looking at them perhaps? I'm wondering if there's a particular page you have open that's causing this to occur.

I don't usually use tabs although I will say that it does tend to happen at odd times when I have more than one window open. The example YouTube crash happens every time however, even if I have only the one window open.

I've noticed that Dashboard will sometimes cause an immediate crash of Omniweb too, even with Flash off. I have a couple of Safari web widgets in my dashboard which could be a contributing factor or not because the crashes are inconsistant.

I am a little surprised that Omni can't catch these crashes and at perhaps just shut down the offending window or go back to the previous page or something. Seems like whatever the issue is it's scrambling OmniWeb but good.

[Daddy Warpig]

Went away after disabling the 1Password extension. Otherwise, the problems seem the same: 10.6.2, latest version Omniweb, errors in console about the "CGContextSetFontRenderingMode".

There was also an error about 1Password conflicting with Omniweb:

Dec 20 21:26:18 thismacintosh [0x0-0x1b01b].com.omnigroup.OmniWeb5[212]: objc[212]: Class OADatePicker is implemented in both /Applications/OmniWeb.app/Contents/Frameworks/OmniAppKit.framework/Versions/A/OmniAppKit and /Users/thisuser/Library/Application Support/1Password/Extensions/30383/WebKitExtension.bundle/Contents/MacOS/WebKitExtension. One of the two will be used. Which one is undefined.

Quick update: this problem may not be solely Omni-web related. I reenabled the 1Password extension, and everything ran fine. The exact same tabs, exact same sites, no problems.

The problem happens every time I start one app that has the 1Password extension, while another app that uses the same extension is running.

Launch Omniweb, no problem. Launch Camino, no problem.

Launch Camino while OW is running (or vice versa), terminal system slowdown and nothing else will launch. Nothing.

Hope this helps.

[AlanBDahl]

What is the "1Password" extension and how is it configured? I've never heard of it before.

[Daddy Warpig]

What is the "1Password" extension and how is it configured? I've never heard of it before. 1Password is a password management program. It remembers passwords for you, so you don't have to.

It has a plugin for Web Browsers that allows it to enter your password when you go to a site. For the Omniweb forums, instead of typing in the username/pword in the upper right, I click on the 1P button and it enters them for me.

This allows you to have a different password for each site, including unguessable passwords (20-digit random alpha-numeric strings), and hence greater security.

Website: http://agilewebsolutions.com/products/1Password

[AlanBDahl]

1Password is a password management program. It remembers passwords for you, so you don't have to.

Ok, well I am not using that, I just let keychain remember them for me which is the OmniWeb default behavior.

[AlanBDahl]

Looks like I may have solved the problem. Font Book has been reporting duplicate fonts for Arial Rounded Bold, Courier New, Courier New Bold and Webdings when I check for duplicates for all fonts even though I've ran "resolve duplicates" many times and no duplicate warning triangles display in the tree view.

What I did was re-enable all the duplicates for those fonts, then I rebooted and resolved duplicates again and then rebooted once more. After that everything seemed to work ok. My guess is that an earlier Resolved Duplicates from before I had Snow Leopard resolved in favor of an older font and disabled a font that Webkit now requires. Anyway that trick appears to have worked for me and it's worth a try for anyone else experiencing problems with fonts related to Omniweb and Flash.

Thanks to everyone on the forums for their suggestions on how to fix my problem!

[AlanBDahl]

Figured out what was going on. The solution is here (http://forums.omnigroup.com/showpost.php?p=71024&postcount=22).

[Brian]

merged threads.

[yb8]

Just to say, I'd had the same crash problems since upgrading to Snow Leopard a couple of weeks ago. The font solution worked for me too, so thanks to all involved in working it out, and for putting the answer somewhere public.