[TR] Test report

[DemonWitch]

Tag
{mvn_version}

OS (linux/windows/macosx)
macosx

Version/Flavor (e.g. Ubuntu 20.04, Windows 10, Big Sur)
macOS 12.3.1 (12.3.1)

Arch (amd64/i386/arm64/arm)
arm64

Report as working? (Y/N)
N

Did you test with the official sample app? (Y/N)
Y

Additional information
run with error :
....
[0530/153434.107048:WARNING:gpu_process_host.cc(1292)] The GPU process has crashed 9 time(s)
[0530/153434.107075:FATAL:gpu_data_manager_impl_private.cc(417)] GPU process isn't usable. Goodbye.

[Friwi]

@DemonWitch Which version were you using?

[Friwi]

As this issue was common with older versions and no version info was provided yet, I will close this for now. Please test with an up to date version, if you did not already.

[DemonWitch]

here is my gradle settings:
plugins {
id("org.jetbrains.intellij") version "1.5.2"
java
}
dependencies {
implementation("me.friwi:jcefmaven:100.0.14")
}
intellij {
version.set("2022.1.1")
}

---

and my idea version is also "2022.1.1"

[Friwi]

Are you trying to run jcefmaven from a plugin inside intellij idea? IntelliJ probably modifies a lot in its own environment which might clash with jcefmaven. Apart from that, intellij already bundles jcef alongside itself. I'd recommend to just use the jetbrains-cef included in intellij. I'm not sure if the (technically) same native library can be used twice in parallel from one java process. Feel free to comment on this issue if you have any new insights concerning this topic. I currently do not have a test environment to actively test this edge case on macosx.

[DemonWitch]

Maybe it's not about jcefmaven itself, neither intellij idea.
It's about the OS and Chrome kernel adaptation, when I added a parameter '--in-process-gpu' of Chrome with api jcefmaven provided:

CefAppBuilder builder = new CefAppBuilder();
builder.addJcefArgs("--in-process-gpu");

The error was gone.
But only use this single parameter may cause other errors, so here is my full config:

      builder.addJcefArgs("--in-process-gpu");
      builder.addJcefArgs("--single-process");
      builder.addJcefArgs("--disable-in-process-stack-traces");
      builder.addJcefArgs("--use-mock-keychain");
      builder.addJcefArgs("--disable-features=SpareRendererForSitePerProcess");

After that , JCEF works fine in my environment.

[Friwi]

Thank you for experimenting with the configuration and finding a solution. In case this becomes a problem for more users I will consider to use this as a default configuration on macos arm64 :)