Aleksei Khoroshilov

every instance is out of memory. swap increase or RAM increase should solve this.

OOM might not be the issue [1], but a bug in `lld` or some other memory-related bug. `malloc_report` is trying to report something, but to see the data we should...

> Got a command for this? dump syslog: `cat /var/log/system.log` dump last 10 minutes of Apple System Log: `log show --last 10m`

> but I don't know what patterns we're looking for... me neither :) if you can run the ASL dump right after the `npm run build` failure, then we can...

after adding `export MallocDebugReport=crash` we got this: ``` 20:12:46 ld64.lld(2483,0x70000dc21000) malloc: *** error for object 0x6000c26fd110: pointer being freed was not allocated 20:12:46 ld64.lld(2483,0x70000dc21000) malloc: *** set a breakpoint in...

got this during one of the reproduce runs, but it’s unclear if this is the initial culprit or an aftermath of a crash. this is a fatal error that aborts...

`PermissionLifetime` should work for this. Currently `BraveEthereumPermissionContext` with UI part is quite customized and doesn't set lifetime setting. It needs to call `PermissionRequest::SetLifetime` and `PermissionLifetimeManager::PermissionDecided` for `PermissionLifetimeManager` to properly track...

@bridiver @mkarolin @petemill PTAL

> Since there's a lot going on in this PR (it fixes a few things), could you briefly describe which one fixes the v8 sync issue? the v8 issue is...

@bridiver @petemill ptal.