Skip to content

Viewer builds incorporating CEF 139 results in transient errors at page loadΒ #4575

@callumlinden

Description

@callumlinden

Environment

Internal test build of Viewer from this PR

Might be Windows only - the macOS build is too slow to test right now

Description

After CEF 139 was incorporated into a test Viewer, it was noticed that various pages (most often the Viewer login page) result in a short transient error being displayed, before the content resolves as expected.

  • Other people apart from myself have seen it so it's not my network
  • It appears to have started after CEF version 134
  • When the error occurs, CefBrowserHandler::onLoadError() is triggered
    • Note, historically this was often triggered with a value of ERR_ABORT (-3) which according to the official instructions, can be safely ignored. The errors we see in this issue are different - often -15.
  • It was been seen outside of the Viewer in the Dullahan test app
  • It has been seen for other non-Linden URLs but it happens less frequently
  • Tried adding a handler for CefRequesatContext::onRequestContextInitialized() and proceeding with the application after that completes but that didn't appear to help

What is left to try?

  • Not much sadly but this on my list:
  • Write something to only update the memory buffer when an HTTP status code of 200 (maybe) is received. Since the error does resolve in a short period, this would just appear as a slight delay loading a page and the error would never be displayed.
  • Write a small, terminal based CEF app that illustrates the issue. Text only. No Viewer. No textures. Shouldn't take more than a day. It might tell me something and if not, more likely to get help from other CEF people than asking them to build the Viewer.
  • "Hope it goes away in a later version of CEF" - pretty thin!

Reproduction steps

Simply start the Viewer - about 20% of the time, you see the transient error before the login page resolves.

Example:

Image


This repo is using Opire - what does it mean? πŸ‘‡
πŸ’΅ Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
πŸ•΅οΈβ€β™‚οΈ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
πŸ™Œ And when they open the PR, they can comment /claim #4575 either in the PR description or in a PR's comment.

πŸͺ™ Also, everyone can tip any user commenting /tip 20 @callumlinden (replace 20 with the amount, and @callumlinden with the user to tip).

πŸ“– If you want to learn more, check out our documentation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtriageFlags issues that need to be triaged

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions