PF4Public

You need to rebuild electron with that flag, not vscode

> with the "trace breakpoint" error This issue appears often and I don't have a solution for it (so far). Just try again and again.

> I suppose the next reasonable step is to build Electron 31 with the flag set Of course! The issue persists as it doesn't bother Google enough to fix it.

@nethershaw Your issue might be a separate one then. Like #380 maybe.

I'll call it "resolved" then :)

I can reproduce this on a non-bin version. Might be helpful to build a debug version. It might be also a good idea to try another ungoogled-chromium binary (perhaps even...

Riiiigggght! If it has something to do with font rendering, I can speculate that Fontations is insufficiently good removed here: https://github.com/PF4Public/gentoo-overlay/blob/f1283d3fd27cb13a34dbd876cced7c8ac27d0736/www-client/ungoogled-chromium/ungoogled-chromium-129.0.6668.89_p1.ebuild#L471-L480

It could help of someone could build a debug version and obtain a backtrace from a crash.

@brianpardy `debug` flag was often malfunctioning, but you don't need to build it that way, `-ggdb3` (as suggested on https://wiki.gentoo.org/wiki/Debugging) should suffice. Besides, `debug` adds other codepaths, which could potentially...

> Enabling the -ggdb3 flag also causes issues. Are you speaking for electron? Could be. Chromium - unlikely. I've built it that way many times without issues.