Version-Release number of selected component: midori-0.4.7-2.fc18 Additional info: backtrace_rating: 4 cmdline: midori crash_function: WebKit::FrameLoaderClient::dispatchWillSendRequest executable: /usr/bin/midori kernel: 3.7.8-202.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 WebKit::FrameLoaderClient::dispatchWillSendRequest at /lib64/libwebkitgtk-1.0.so.0 #1 WebCore::ResourceLoadNotifier::dispatchWillSendRequest at /lib64/libwebkitgtk-1.0.so.0 #2 WebCore::ResourceLoader::willSendRequest at /lib64/libwebkitgtk-1.0.so.0 #3 WebCore::MainResourceLoader::willSendRequest at /lib64/libwebkitgtk-1.0.so.0 #4 restartedCallback at /lib64/libwebkitgtk-1.0.so.0 #9 soup_message_restarted at soup-message.c:1125 #10 process_queue_item at soup-session-async.c:260 #11 run_queue at soup-session-async.c:310 #12 idle_run_queue at soup-session-async.c:343 #18 gtk_main at gtkmain.c:1257
Created attachment 699472 [details] File: backtrace
Created attachment 699473 [details] File: cgroup
Created attachment 699474 [details] File: core_backtrace
Created attachment 699475 [details] File: dso_list
Created attachment 699476 [details] File: environ
Created attachment 699477 [details] File: limits
Created attachment 699478 [details] File: maps
Created attachment 699479 [details] File: open_fds
Created attachment 699480 [details] File: proc_pid_status
Created attachment 699481 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate it?
ups, very fast reply. thanks! i write msg and use the "search tool" from a SM* webside. the seach works whit JS (IMHO) on this day (i submit the bug) the crash came up 3 times on one webside (social media*). today i test it on the same website. no chrashes. the side use javascript an flash (many advertising) very excessive
Strange. ok. Will see if I can make anything from the backtrace.
Moin ;) some observations too: everytime i start midori: #[user@kiste ~]$ midori #(midori4:2112): GLib-GIO-CRITICAL **: g_file_get_parent: assertion `G_IS_FILE (file)' failed # #(midori4:2112): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed # #(midori4:2112): GLib-GIO-CRITICAL **: g_file_get_parent: assertion `G_IS_FILE (file)' failed # #(midori4:2112): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed # # a second issue: sometimes i see/have "favicons" in my bookmarks - sometimes (the most time) i dont have/see favicons on my bookmarks. i see favicons only at Tabs, but not in my Bookmarks. (Attachment:midori-favicons.png.zip) btw: thanks for a great pice of software.!!!
Created attachment 700451 [details] midori-favicons.png.zip - Screenshots Midori-GUI
i am online on a social media "webside" ... midori crashes, kernelcrashes cames twice backtrace_rating: 4 Package: midori-0.4.7-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.