Midori displays a message: Oops - http://www.ig.com.br Something went wrong with http://www.ig.com.br [Try again] When started in a terminal, several messages are displayed about theme parsing errors, which appear to be not directly related to the rendering error shown above. It's interesting to note that Mageia's home page, Slashdot.org, among other sites render without any problem whatsoever. That iG page also renders almost in its entirety, including pics. It looks like some element (an ad?) made Midori quit. How reproducible: Error does not occur with a more modern Intel processor; OTOH, illegal instruction is never mentioned (which is to be expected from an old non-SSE2 CPU). On said older CPU, the problem is systematic. Steps: - Install Mga6 sta1 English and apply updates. - Install Midori. - Go to the above address. - While rendering the page the screen is cleaned and the error message shown. BTW, congratulations to Mageia builders for a work well done, it's a pleasant surprise to see Midori working on i586 hardware (actually, the CPU is an i686, but without the SSE2 instruction). Simple sites are handled very well; more complicated ones like Slashdot.org might need some tweaking as they work better in Firefox.
Maybe I spoke too early: Got these two lines in dmesg after Midori oopsed on a page: [ 145.314820] traps: WebKitWebProces[2524] trap invalid opcode ip:ac3e5656 sp:bf910be0 error:0 [ 145.314908] audit: type=1701 audit(1477257768.628:163): auid=1000 uid=1000 gid=1000 ses=1 pid=2524 comm="WebKitWebProces" exe="/usr/libexec/webkit2gtk-4.0/WebKitWebProcess" sig=4 It seems this is just a cleaner way to deal with an "illegal instruction". Oh, well... [Aside: BTW, after installing Qupzilla it won't be able even to render its own empty homepage (qupzilla:start), nor a simple site I chose. It loops trying to restart the page rendering until it quits after many tries. dmesg gets plenty of these "traps" and "audits". A lot has already been talked about Qt5, maybe there's no need to file a bug about Qupzilla.] But I think at least Midori is onto something. Since it already renders well the more basic pages, it seems there's an intention to make it work on weaker PCs.
Changed priority to reflect the probably low number of affected computers; OTOH it is of major severity, because some pages won't be rendered at all. Please note that, contrary to description and as per comment #1, there is a cleaner handling of the invalid opcode problem (which therefore indeed occurs) -- instead of crashing the application, the error is trapped, a message generated in dmesg and an empty page prompts the user to try a new access to the problem page.
Summary: Midori oops on a heavy page with an old CPU => Midori oops on some webpages - with old non-SSE2 CPUSeverity: normal => majorPriority: Normal => Low
For a (very) extended discussion of the problems arising from the decision to no longer support processors without Intel's SSE2 opcode -- and a discussion on the meaning of life as well :-/ -- please see Bug 15594. In comment #17 there, I thought about separating that report in three bugs: one for Midori (the present one), one for Plasma (Bug 19258) and one about Qupzilla (which I won't open right now, because I understand there's an overlap with the Plasma issue, Qt5 requiring SSE2 being the primary reason for that). Bug 19258 has a discussion (with links) about CPUs without SSE2 and why machines with such processors are not necessarily feeble. Also there's a link there about a warning from Mozilla about end-of-support in Firefox for such processors.
Source RPM: (none) => midoriCC: (none) => marja11Assignee: bugsquad => cvargas
I think the problem is in webkit. What features does the computer on which you have the problem?
Let me see... Chromium-browser aborts: Illegal instruction (core dumped), when ran in a terminal window. Qupzilla refuses to start: "This program requires an x86 with the the SSE2 extension, which your CPU lacks" or something to that effect. Midori starts, it Oops now and then, but when I turn off Midori's option to run scripts, the Oops cease -- but then again many things won't work anymore. Firefox runs without problems, but Flash won't work in its most recent version; HTML5 videos are ok. And IIRC vlc/mplayer can play Flash videos should it be needed. Other things seem to work.
Some clarifications: I wish to acknowledge that turning off Midori's "Enable scripts" option to avoid crashes was found in an on-line comment; it was not my personal finding. In nowadays Internet, disabling JavaScript can render some pages unusable... thus not exactly a helpful workaround. The Flashplayer-plugin won't work because of SSE2, too, as stated in this page: http://cromwell-intl.com/linux/flash-on-non-sse2-cpu.html
(In reply to Renato Dali from comment #5) > Firefox runs without problems, but Flash won't work in its most recent > version; HTML5 videos are ok. And IIRC vlc/mplayer can play Flash videos > should it be needed. Try with npapi version of flash the ppapi flash give troubles too Uninstall the freshplayer plugin and if you don't use the ppapi flash plugin
As CPU's without SSE2 are nearly 20 years old and nearly nobody uses this nowadays... We shouldn't put more effort into dying/already dead hardware compatibility. Closing as OLD
Status: NEW => RESOLVEDResolution: (none) => OLD