Bug 1305994

Created attachment 1122477 [details]
File: backtrace

Created attachment 1122478 [details]
File: cgroup

Created attachment 1122479 [details]
File: core_backtrace

Created attachment 1122480 [details]
File: dso_list

Created attachment 1122481 [details]
File: environ

Created attachment 1122482 [details]
File: limits

Created attachment 1122483 [details]
File: maps

Created attachment 1122484 [details]
File: mountinfo

Created attachment 1122485 [details]
File: namespaces

Created attachment 1122486 [details]
File: open_fds

Created attachment 1122487 [details]
File: proc_pid_status

Created attachment 1122488 [details]
File: var_log_messages

In my environment the crash occurs at the following URL: http://heise.de/-3269980

The content is dynamic, I don't know if will occur in the future too.

Version of midori:

midori -V

Midori 0.5.11 ((null)) Midori
GTK+ 2.24.28 (2.24.30)	Glib 2.45.6 (2.46.2)
WebKitGTK+ 2.4.9 (2.4.11)	libSoup 2.51.90
cairo 1.14.2 (1.14.2)	libnotify No
gcr 3.16.0	granite No

Copyright (c) 2007-2013 Christian Dywan

Fedora version (23):

uname -a
Linux 4.4.9-300.fc23.x86_64 #1 SMP Wed May 4 23:56:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux


I've started midori with debug enabled:

midori -g
Launching command: '/usr/bin/gdb' --batch -ex 'set print thread-events off' -ex run -ex 'set logging on /run/user/1000/midori/gdb.bt' -ex 'bt' --return-child-result --args midori 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Detaching after fork from child process 17521.
openjdk version "1.8.0_92"
OpenJDK Runtime Environment (build 1.8.0_92-b14)
OpenJDK 64-Bit Server VM (build 25.92-b14, mixed mode)
Vector smash protection is enabled.

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff13ea190 in JSC::JSCell::getPrimitiveNumber(JSC::ExecState*, double&, JSC::JSValue&) const () from /lib64/libjavascriptcoregtk-1.0.so.0
#0  0x00007ffff13ea190 in JSC::JSCell::getPrimitiveNumber(JSC::ExecState*, double&, JSC::JSValue&) const () at /lib64/libjavascriptcoregtk-1.0.so.0
#1  0x00007ffff13b153c in slow_path_less () at /lib64/libjavascriptcoregtk-1.0.so.0
#2  0x00007fff8d5e6c61 in  ()
#3  0x00007fff656c72b0 in  ()
#4  0x00007ffff7eaf000 in  ()
#5  0x00007fff641b2a30 in  ()
#6  0x00007fffffffd070 in  ()
#7  0x00007fff65ad1ff8 in  ()
#8  0x00007fffffffd080 in  ()
#9  0x00007fffffffd000 in  ()
#10 0x00007ffff129bc13 in JSC::JITCode::execute(JSC::VM*, JSC::ProtoCallFrame*, JSC::Register*) () at /lib64/libjavascriptcoregtk-1.0.so.0


midori -g
Launching command: '/usr/bin/gdb' --batch -ex 'set print thread-events off' -ex run -ex 'set logging on /run/user/1000/midori/gdb.bt' -ex 'bt' --return-child-result --args midori 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Detaching after fork from child process 18324.
openjdk version "1.8.0_92"
OpenJDK Runtime Environment (build 1.8.0_92-b14)
OpenJDK 64-Bit Server VM (build 25.92-b14, mixed mode)
Vector smash protection is enabled.

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff13ea190 in JSC::JSCell::getPrimitiveNumber(JSC::ExecState*, double&, JSC::JSValue&) const () from /lib64/libjavascriptcoregtk-1.0.so.0
#0  0x00007ffff13ea190 in JSC::JSCell::getPrimitiveNumber(JSC::ExecState*, double&, JSC::JSValue&) const () at /lib64/libjavascriptcoregtk-1.0.so.0
#1  0x00007ffff13b153c in slow_path_less () at /lib64/libjavascriptcoregtk-1.0.so.0
#2  0x00007fff8d81c01b in  ()
#3  0x0000000000000000 in  ()

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reopened: Error occurs on Fedora 23 too.

Error occurs on Fedora 24 too.

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.