Ah, that should explain my own issues, too.
I'm using Catalina's successor, Big Sur (11.7.9), also deprecated by Apple. 1.32.0.24 (and the yet-experimental 1.32.1.7) both crash-upon-launch, and the only thing in the logs that really stands out is, on
cef_log.txt:
This seems, indeed, to be
related to CEF, although I don't really understand where that error currently comes from — much less how this can be fixed. I'm assuming, since this is a C# file, that it belongs to the Google-provided Chromium code — not part of the viewer code! — right?
I also wonder... is there a way to launch the Cool VL Viewer
without CEF support, with parameters on the command line? I'm just asking this because there are
a lot of options there for the command line, but I couldn't pinpoint the one that turns CEF completely off. You can also selectively
change the debug settings using the
--set argument, but, alas, in my case, I see absolutely no difference — Cool VL Viewer just launches and crashes when trying to open the CEF-enabled "splash screen". My hope was that, by supplying the avatar name & password, it would ignore the "splash screen" and log in directly to SL, but I'm afraid this is
not how it works... unless, as said, there is a setting somewhere that I've completely overlooked!
Note that, in over 99% of the cases, I don't
need MoaP — except when debugging something which
does use it! — and so I can live happily without it, at least until this specific issue is fixed or gets a workaround. In other words: sure, I'm more than fine to forfeit the in-world browser & MoaP in exchange for the ability to log in
Also, for future reference, I'm enclosing some selected tidbits on my startup logs; essentially what caught my attention. Besides CEF, it seems that my ancient Mac is struggling with loading the advanced shaders — no surprises there, especially because Cool VL Viewer seems to be launching OpenGL 2.1 out of caution, even though my Nvidia card is more than eager to deal with 4.1 — but it is unusual. The rest is mostly related to MoaP, CEF, etc. Notice the very clean shutdown which finally ends with a memory segmentation fault
after everything else was properly disposed with! (very nicely coded!)