Closed GlenDC closed 1 year ago
This problem resolved itself on our end, without any changes. But no clue why this was.
is it possible because problems on the side of target? But if so, that wouldn't explain this error, right?
Was this on boot-up? Or did it suddenly stop? In either case, this error means Chrome wasn't able to launch on your machine. Is it possible your machine was auto-updating a shared lib on the machine?
Better logging would probably be useful there.
There are a bunch of logs you can see if you turn on more verbose logging or look in the session databases, but the same logs are often just noise. If you have a session db, I can see if there's anything we should have bubbled up.
Hmm. Going to see if perhaps i should somehow have that info exposed in our layer logs for such cases. Will come back to you if needed.
Going to close it, hasn't popped up since I reported it.
My process no longer wishes to start a new Hero instance, with this as a trace. The logs say nothing extra either.