Bug 225313
| Summary: | [GTK] MiniBrowser segfaults with my banking website | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Dennis Nezic <dennisn> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Major | CC: | bugs-noreply, cgarcia |
| Priority: | P3 | Keywords: | Gtk |
| Version: | WebKit Local Build | ||
| Hardware: | PC | ||
| OS: | Linux | ||
Dennis Nezic
MiniBrowser, and a few others (eg. midori and badwolf) segfault during the loading of https://secure.pcfinancial.ca/login
I have had at least one other person on IRC confirm this segfault, with badwolf.
I can see the spinning loading circle, so it is able to start processing some of the webpage.
Oddly enough (very oddly!), it works fine with "surf"!? Why would webkitgtk's own MiniBrowser fail, but "surf" work?
Also odd is how midori will segfault even faster if I subsequently try to simply start typing the url ... it tries to autocomplete it, or fetch something from history, or something. It doesn't even begin loading the page, in order for this segfault to happen! Clearing my cookies and history and other state files obviously avoids this url-autocompletion path to the segfault.
midori: segfault in libwebkit2gtk-4.0.so.37.53.1
MiniBrowser: segfault in libwebkit2gtk-4.0.so.37.53.1
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Carlos Garcia Campos
*** This bug has been marked as a duplicate of bug 225279 ***