[2.1.0.9] Browser starts and hangs
Updated to 2.1.0.9. The default sailfish browser worked fine for one day or so. After some jolla restart it stopped to work correctly: now the browser starts, then hangs a moment while trying to unsuccessfully open the default home page (the together jolla webpage), and finally flickers a blank page and minimizes. No way to change the url, settings or do anything. Removing and reinstalling sailfish-browser from the command line with pkcon didn't help either. Alternative browsers seem to work so far. Any help greatly appreciated, since I prefer using the original browser.
without posting relevant stderr output when sailfish-browser is started via terminal, I think nobody is really able to help...
lpr ( 2017-02-11 14:22:16 +0200 )editI can confirm this issue. You can work around if clicking quick on the little tab counter on the bottom left. In the tab view clode all tabs. If you are to slow, the browser closes.
[code]
[/code]
jolladiho ( 2017-02-11 20:58:22 +0200 )editthe log above is from opening the browser: if the browser was closed with a tab opened to download a file or trying to open this link at startup: http://repo.merproject.org/obs/home:/kimmoli:/tohs/sailfishos_2.1.0.9/armv7hl/harbour-ambience-tohkbd2-0.5.23-78.1.armv7hl.rpm
jolladiho ( 2017-02-11 21:20:45 +0200 )editSame here. Does not seem related to a specific website, and seem quite random : a page loading properly one time can crash the browser the next time. Log is quite similar to the one posted by jolladiho : segfault without meaningful (at least to me) warning.
grmoht ( 2017-02-16 11:05:13 +0200 )editI have the exact same problem after updating a Jolla 1 to Haapajoki (2.0.5.6)and the log is almost identical to @jolladiho's !! For me, it happens only at a specific website (https://derkleinelionel.jimdo.com/) and I can also prevent the crash by quickly changing to the tabs view. If I now open a different website or change to an already existing tab, the browser doesn't crash but if I change back to the offending website, the crash (Segmentation fault) occurs.
Addition:
The system log (via "journalctl") shows an "unhandled page fault" every time the crash occurs:
Kohle ( 2017-03-05 21:25:12 +0200 )edit