search

bitwiseworks / qtwebengine-chromium-os2

Port of Chromium and related tools to OS/2
9 stars 2 forks source link

simplebrowser: Site can't be reached after process crash #47

Open dmik opened 2 years ago

dmik commented 2 years ago

If a simplebrowser process crashes while viewing some URL, any subsequent attempt to view this URL after a restart will end into the web site being unreachable with the following error message:

image

It seems that the problem affects HTTPS URLs more often that HTTP ones. And not all HTTPS sites are affected, for example https://google.com and https://yandex.ru seems to work even after crashing.

Steps to reproduce:

  1. Clean up simplebrowser's cache with rm -rf %HOME%/.cache/QtExamples/simplebrowser.
  2. Start /@unixroot/usr/lib/qt5/examples/webenginewidgets/simplebrowser/simplebrowser.exe w/o arguments -- it should open https://www.qt.io cleanly.
  3. Kill the main simplebrowser.exe process with kill -9.
  4. Start the browser again and you will see the above screenshot.

A temporary workaround for this problem is to clean up the cache as shown in step 0.

dmik commented 2 years ago

Note that the very same problem is observed with otter-browser.exe as well (and perhaps with any browser based on QtWebEngine 5.15.2 so.far). The workaround for Otter is to delete its cache dir as well with the following command:

rm -rf %HOME%/.cache/Otter
TeLLie commented 2 years ago

Hi, I don't see this behavior on my laptop nor on my test desktop. I notice this behavior in earlyer builds from otter-browser i did, but when I saw this it where with plain os2, not under os4. Not sure if this is relevant to mention...

DavidMcKenna commented 2 years ago

I also do not see this problem... the web page always comes up on start even after killing the simplebrowser process.