Solved QtWebEngine 5.10.0 configuration problem
-
Since installing 5.10.0 I am encountering errors whenever I attempt to load an url using either QWebEnginePage or QWebEngineView. I even attempted to build and run the SimpleBrowser example and obtain the same error as listed below.
[8812:8948:0105/224424.704:ERROR:icc_profile.cc(60)] Failed to parse ICC profile to SkICC.
[8812:6116:0105/224427.021:ERROR:launch_win.cc(313)] Command line:
"C:\Qt510\5.10.0\msvc2015_64\bin" --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --disable-mojo-local-storage --no-sandbox --enable-features=AllowContentInitiatedDataUrlNavigations --service-pipe-token=B53C7A7E7D30F16EFBD50A28F6767E73 --lang=en-US --enable-pinch --device-scale-factor=1 --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;0,16,3553;0,17,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;1,16,3553;1,17,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;2,16,3553;2,17,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553;3,16,3553;3,17,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553;4,16,3553;4,17,3553 --disable-accelerated-video-decode --disable-gpu-compositing --enable-gpu-async-worker-context --service-request-channel-token=B53C7A7E7D30F16EFBD50A28F6767E73 --renderer-client-id=2 --mojo-platform-channel-handle=1768 /prefetch:1
: Access is denied. (0x5)I have tried several clean reinstalls to no avail. Any ideas?
-
I reverted to 5.8 and all is well again.
-
As a follow-up, turns out Malwarebytes had quarantined QtWebEngineProcess and was blocking execution