chore: stabilize current head before Phase 10a QC
This commit is contained in:
@@ -12,9 +12,7 @@ use tauri::Manager;
|
||||
|
||||
use magnotia_core::types::EngineName;
|
||||
use magnotia_llm::LlmEngine;
|
||||
use magnotia_storage::{
|
||||
database_path, get_setting, init as init_db, prune_error_log, set_setting,
|
||||
};
|
||||
use magnotia_storage::{database_path, get_setting, init as init_db, prune_error_log, set_setting};
|
||||
|
||||
/// How long to retain `error_log` rows. Pruned once on startup.
|
||||
/// 90 days is long enough to triage "this happened a few weeks ago"
|
||||
@@ -117,7 +115,11 @@ fn ensure_x11_on_wayland() {
|
||||
// magnotia idle CPU 12.30% → 2.80% of one core and idle GPU 17% → 10%.
|
||||
// Apples to both X11 and Wayland sessions; users can opt back in by
|
||||
// setting WEBKIT_DISABLE_DMABUF_RENDERER=0 explicitly.
|
||||
set_if_unset("WEBKIT_DISABLE_DMABUF_RENDERER", "1", "iGPU idle-cost workaround");
|
||||
set_if_unset(
|
||||
"WEBKIT_DISABLE_DMABUF_RENDERER",
|
||||
"1",
|
||||
"iGPU idle-cost workaround",
|
||||
);
|
||||
|
||||
// If the user is on a Wayland session, also force WebKitGTK + GDK
|
||||
// onto X11 via XWayland. Idempotent: if a value is already set, keep
|
||||
|
||||
Reference in New Issue
Block a user