Is there anything funny about the Wired site?

[hazel]

The Forum eBulletin contains a lot of interesting articles from wired.com. I can reach these easily using graphical Links or Firefox, but for some reason Midori always chokes on them. It hangs halfway through the download and then crashes. Obviously this is a bug in Midori but I would dearly like to know what triggers it. It doesn't happen on any other site, only on Wired.

[atreyu]

hazel,

Can you provide a link? I am surfing wired.com on Midori w/no probs, but I don't see any forum links that I can click on...

Midori4 0.4.6.
Fedora 17

[hazel]

Ok, here is a typical example:http://feeds.wired.com/%7Er/wired/in...3/fec7euPjmvc/
As you can see, it's redirected from a feeds site: all of them are the same except for the last element.

[atreyu]

well, the page opens on midori for me, not without some griping though. this is what i get in the terminal from which I launched midori:

** Message: console message: http://www.wired.com/js/cn.minified.js?ver=20120831 @1: INFO, :: ,CN Ad Plugin Skipped, :: ,CN Ad User Agent Plugin, :: ,[object Object]

** Message: console message: http://www.wired.com/js/cn.minified.js?ver=20120831 @1: INFO, :: ,CN Ad Plugin Skipped, :: ,CN Ad Param-based Modifiers, :: ,[object Object]

** Message: console message: http://www.wired.com/js/cn.minified.js?ver=20120831 @1: INFO, :: ,CN Ad Plugin Registered, :: ,CN Ad Lotame Audience kws, :: ,[object Object]

** Message: console message: http://www.wired.com/js/cn.minified.js?ver=20120831 @1: INFO, :: ,CN Ad Plugin Registered, :: ,CN Ad Yieldex, :: ,[object Object]

** Message: console message: http://connect.facebook.net/en_US/all.js @54: FB.getLoginStatus() called before calling FB.init().

** Message: console message: http://connect.facebook.net/en_US/all.js @54: FB.init has already been called - this could indicate a problem

i don't know if that helps you any, but at least i can say the link is working for me...

[hazel]

I was running it directly out of Claws-mail, but I've just tried from a terminal (now why didn't I think of that myself?).

I got a different set of error messages from yours:

** (midori4:296): CRITICAL **: sokoke_js_string_utf8: assertion 'js_string' failed
** (midori4:296): WARNING **: (null)
Segmentation fault midori

I don't know if the reported javascript error is what caused the crash, but I do remember reading somewhere that Midori is still unstable code and has a habit of crashing. Anyway, I've reinstated links as my ancilliary browser for email and that solves the problem.

[hazel]

You'll laugh. A Midori update just came down the line. Of course I tried it out at once on a feeds.wired.com link. It's still buggy - takes forever to load the site - but it doesn't crash any more. Evidently someone has been complaining about this and it's been fixed. I looked at the ChangeLog for this version (0.4.7) but I couldn't see anything that I could relate to this.