Crash when opening second site via new tab overview (favourites,popular sites,links from other apps)

I’m not seeing that here on my BQ 4.5 running the latest rc-proposed.

When you say that the browser crashes, can you describe exactly what happens? Are there some crash files under /var/crash/ ?

The browser simply disappears like a crashing app and is to be restarted. By chance I discovered 7000 and 3000 history entries of my two most popular technical sites now. So I deleted them by "settings -> data protection -> delete browser history" in the webbrowser app. Since then the browser has no crashes at the second tab. (Site opening from twitter to webbrowser app doesn't work today, maybe another issue, so I cannot test it.) And it reacts much faster. So the bug could be solved - but:

I have the phone since 6 months but this could only be the history of the last month. Is there a mechanism which deletes history entries older then one month? So for me this is too late because I'm a heavy browser user and read almost everything over the day on my phone. Possible solution: So maybe 1-2 weeks of history should be enough. (In relation: More important would be caching of more then two tabs, this is a really annoying decision and reported from me in Bug #1446904 "browser is limited to 2 live webviews" ).

Okay, there may be an issue with the history model that cannot cope with too many history entries. Have you kept a copy of your history db before clearing it, by any chance? That would be very helpful to investigate the issue. If not, please make a copy (~/.local/share/webbrowser-app/history.sqlite) next time you hit the problem and let me know.

Only the newest version from store didn't crash until now. If the problem reappears a test with a dummy file with 10.000 URLS (for i in 1..9999; do echo...) should crash, too. It seems only to be the amount an not the content itself. I have Ubuntu Phone to not have to share my (10.000 addresses) history with any services if it is so easy to bypass with a bash one-liner. :) But it seems fixed for now and maybe from now on - we will see in future versions.

Yeah I understand you don’t want to share your history db, that’s absolutely fine, I wasn’t even asking for it :)
But if you keep a copy of it before clearing it next time it happens to you, that may help debugging the issue.
Anyway, I’m glad to know that the issue hasn’t happened again so far.