Open Bug 2005415 Opened 2 days ago Updated 2 days ago

Evaluate scheduled vs lazy cleanup for AI Window Security Layer memory management

Categories

(Core :: Machine Learning: General, task)

task

Tracking

()

People

(Reporter: rconcepcion, Unassigned)

References

(Depends on 1 open bug)

Details

(Whiteboard: [genai])

The security layer currently uses lazy cleanup for expired ledger entries: cleanup only happens when the ledger is accessed. This avoids timer complexity but could potentially leak memory if ledgers aren't accessed for extended periods.

An alternative approach is scheduled cleanup using timers to periodically remove expired entries. This ticket is to evaluate the tradeoffs and determine the right approach for production.

Considerations:

  • Memory impact of lazy cleanup with long-idle sessions
  • Timer complexity and overhead of scheduled cleanup
  • Interaction with tab lifecycle (close, restore, navigation)

Acceptance Criteria:

  • Tradeoffs evaluated and approach decided for production
  • If scheduled cleanup is preferred, implement timer-based cleanup
You need to log in before you can comment on or make changes to this bug.