It appears that some test suites can trigger Frame Eviction while running.

FrameEvictionManager is unlocking frames, then subsequent embeddings are triggering evictions:

content::RenderWidgetHostViewAura::AllocateNewSurfaceIdOnEviction()
content::DelegatedFrameHost::EvictDelegatedFrame()
viz::FrameEvictionManager::CullUnlockedFrames()
content::DelegatedFrameHost::EmbedSurface()
....

Since this is tied to memory pressure rates it does mean that frame eviction can incidentally happen on trybots. I'm curious if this could leak to flaky tests. We might want to consider have a test override to better control this

Thoughts?