You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-v did not reach stable-diffusion, leaving every sd run diagnosable only by its errors.sd_log_callback() hard-filtered at SD_LOG_WARN, and sd.cpp installs no printer of its own (log_printf() hands every level to the callback and returns), so chimera sd dropped the whole INFO/DEBUG tier no matter how it was invoked. That tier is where the lines that explain a low-VRAM failure live: Found N backend devices, total params memory size = ... (VRAM x, RAM y), and the model_managerprepared params backend buffer / staged compute params to CUDA0 / releasing compute params sequence. Without them an OOM from weights pinned to the compute backend -- sd's default, since SDBackendManager::params_backend() falls back to runtime_backend() when no --params-backend spec is given -- is indistinguishable from one caused by a placement flag that did not take effect, and the two have opposite fixes. The threshold is now settable (chimera_set_sd_log_verbose()), and -v drops it to SD_LOG_DEBUG. Warnings and errors are unaffected when the flag is absent.
Changed
Global flags now bind after the subcommand as well as before it.app.fallthrough(), so chimera sd -v ... works alongside chimera -v sd ...; previously the former exited with The following argument was not expected: -v. Subcommands bind their own options first, so fallthrough only catches what would otherwise have been an error.