TeamSoftware Solutions

Hi all,

We are testing PWB v3.05.3 with the Chrome rendering engine to see if we want to pay for this product to deploy to our client library public computers. When testing we found a bug, when ClearCacheOnClose=True (what we want for the public) youtube.com will load with an error saying:


"Sorry we are unable to load: https://accounts.google.com/ServiceLogi ... ssive=true

Error (-27): ERR_BLOCKED_BY_RESPONSE"

When I enter the site a second time it loads with no issue, but I get this error on first visit and this could be a problem if we decide to purchase this product for public use, I was wondering if there was word on a fix.

Also I have tested this with the IE rendering engine and the bug does not appear there.

Any info you have on this would be much appreciated.

Thank you

Set/Add the following in the INI file.

[Browser]
ShowChromeErrors=False

This will disable the showing of the CEF errors.

--Scott

Hi Scott,

Thanks for the quick reply. When I put that into the INI file I no longer get the previous error I instead get:

"CEF 3.3538.1850.ge710be4
Chromium 70.0.3538.77
OS Windows
WebKit 537.36 (@0f6ce0b0cd63a12cb4eccea3637b1bc9a29148d9)
JavaScript 7.0.276.32
Flash
User Agent Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36
Command Line "C:\Users\LocalAdmin\Desktop\PWBv3cef\PWB\PWB.exe" --no-sandbox --lang=en-US --log-file="C:\Users\LocalAdmin\Desktop\PWBv3cef\PWB\debug.log" --log-severity=disable --allow-running-insecure-content --enable-system-flash --enable-npapi --enable-media-stream
Module Path C:\Users\LocalAdmin\Desktop\PWBv3cef\PWB\libcef.dll
Cache Path C:\Users\LOCALA~1\AppData\Local\Temp\cache"

Update: I also get this error on ESPN so it's not just a youtube issue.

It does seem to be an issue with the new CEF version PWB 3.05.3 is using and the initial caching.

We are looking into it further.

--Scott

We found the issue and will be posting a fix by the end of the week.

--Scott

PWB version 3.05.4 now available on the Downloads page corrects the error messages.

https://www.teamsoftwaresolutions.com/f ... f=5&t=3281

--Scott

That seems to have done the trick, I will keep on testing and let you know.

Thank you