[Drayon]

Originally Posted by Drayon

The "Magnet Link" bug is still lingering and hasn't been attended to, as of r201127.

When copying a Magnet link via Control+click 'copy link to clipboard' from context menu, then pasting the link to a plain text file or RTF with Command+Option+Shift+V (paste and match style) reveals an incorrect format.

Correct format should be:
magnet:?xt=

OW incorrectly (for some unknown reason), adds a forward slash after the colon:
magnet:/?xt=

Probably a simple 30 second fix, so would like to see it resolved. thanks

I can confirm the following fix:

URL with query but no path — Fixed a bug where URLs with a query but no path (e.g. “magnet:?xt=") would get parsed into a URL with an empty path (e.g. “magnet:/?xt=")

Fantastic, thanks.

[mbert]

I've found another problem. When uploading files in an email in google mail, those attachments get lost when the mail is sent. No error message is displayed, but the mail goes out as if there never had been an attachment.

[mbert]

Build #1230 is rather unstable again, crashes every 5 minutes.

[Ken Case]

Originally Posted by mbert

Build #1230 is rather unstable again, crashes every 5 minutes.

Based on the crash reports, it looks like this is the same crash in the caching code of Apple's frameworks which I've been trying to track down for a while. I was hoping that the changes I made last night for the r201285 build would help, but I've already seen a few crash reports in the same place.

[superhancpetram]

r201285 has been good for me so far; haven’t been able to crash it yet.

[Drayon]

So far, so good here too with r201285.

EDIT-oops, spoke too soon, have been browsing with JavaScript disabled. Renabled it, quit OW, releaunched and bang, crasho. Funnily, then crash catcher itself crashed, and so the report didn’t go through... haha.

Is Command+Control+D on a select word bringing up the “look up” Dictionary for anyone else, as it isn’t here.

[mbert]

Originally Posted by Ken Case

Based on the crash reports, it looks like this is the same crash in the caching code of Apple's frameworks which I've been trying to track down for a while. I was hoping that the changes I made last night for the r201285 build would help, but I've already seen a few crash reports in the same place.

If there was a way to generate the crash report email and display it, so that I can copy and paste and send it to you, I could send you mine, too.

[mbert]

OmniWeb-6-r201776-Test.dmg was the most stable version since OmniWeb-6-r201127-Test.dmg. Subsequent OmniWeb-6-r201813-Test.dmg crashed immediately at startup.

[Ken Case]

Originally Posted by mbert

OmniWeb-6-r201776-Test.dmg was the most stable version since OmniWeb-6-r201127-Test.dmg. Subsequent OmniWeb-6-r201813-Test.dmg crashed immediately at startup.

Hmm, I just upgraded to 201813 and it launched just fine for me (and reopened a few dozen tabs scattered across a number of windows, including this one). Since I haven't been changing anything related to OmniWeb in these builds (which is why the release notes haven't changed), I suspect you're just experiencing the randomness of the crash in Apple's frameworks. (I think it's a timing-dependent concurrency issue.)

[Ken Case]

Originally Posted by mbert

If there was a way to generate the crash report email and display it, so that I can copy and paste and send it to you, I could send you mine, too.

The crash reporter just opens a Compose window in Mail, it doesn't require that you send it there. (You can copy and paste it into something else.)

Mail does require that you configure an account before it will open a Compose window, but it could be any account on any mail server—and once it's set up you can tell Mail to go offline and not actually use it.