[Ken Case]

Originally Posted by mbert

I can't confirm this. Still experiencing crashes of varying frequency.

The same crash in Apple's frameworks which I was trying to track down in December is still there, unless they've fixed it in the OS. Which I don't think they have, since I just got another one this morning. :) But its frequency can be quite variable: sometimes I'll go for weeks without crashing, but other times I'll crash three times in an hour.

I think the only way for me to work around that crash is to write a replacement for that whole module of Apple's code, but I'm not going to have time to do that until my next vacation.

[Tesseract]

Filling usernames and passwords from the keychain seems to have broken sometime in the last few builds.

[Mr.EMan]

Most of the recent builds in the last couple of weeks seems to have de-volved for me. Rendering certain sites are just a mess. Examples for me include:

http://www.accuweather.com/

as well as many pages in amazon.com, like this one:

Sandisk Flashdrive

These all look fine in v5.11.

[Ken Case]

Originally Posted by Mr.EMan

Most of the recent builds in the last couple of weeks seems to have de-volved for me. Rendering certain sites are just a mess. Examples for me include:

http://www.accuweather.com/

as well as many pages in amazon.com, like this one:

Sandisk Flashdrive

These all look fine in v5.11.

This should be fixed in the next build (r209434 or later).

[Mr.EMan]

Originally Posted by Ken Case

This should be fixed in the next build (r209434 or later).

Thanks! Fixed in r209437.

[Ken Case]

Originally Posted by Tesseract

Filling usernames and passwords from the keychain seems to have broken sometime in the last few builds.

This seems to be working fine for me in the current build—assuming OmniWeb has access to the keychain entries in question.

A couple things you might try are quitting and restarting the app, and opening a keychain entry that isn't working in Keychain Access where you can double-check its Access Control settings to ensure that OmniWeb 6 is allowed to use that entry.

[mbert]

Ken, I assume that new builds are only created and added to the staging area if there were some changes in the VCS, is that correct? If yes, this would mean that OW6 receives frequent code changes (even if they'll probably be small) - or am I misjudging my observations here?

[Ken Case]

Originally Posted by mbert

Ken, I assume that new builds are only created and added to the staging area if there were some changes in the VCS, is that correct? If yes, this would mean that OW6 receives frequent code changes (even if they'll probably be small) - or am I misjudging my observations here?

Well, yes and no.

Yes, OmniWeb 6 only builds when code it uses changes. However, it shares a lot of framework code with our other apps, so most of its builds are triggered by framework changes that don't affect OmniWeb's core functionality (or help with its core issues).

Whenever I touch the OmniWeb code base itself, I try to add an entry to the change log so you'll know what's new. So until today, there hadn't been any interesting changes to OmniWeb itself since last December (even though there have obviously been quite a few builds happening in that time).