mirror of
https://github.com/Comfy-Org/desktop.git
synced 2026-11-04 23:47:43 +00:00
[GH-ISSUE #1721] [Bug]: Version 0.9.1 can not start success #523
Labels
No labels
area: desktop-app
Bounty
bug
bug-cop:answered
bug-cop:response-received
component: installer
component: preload
custom node
dependencies
Design
documentation
duplicate
enhancement
expected
frontend
good first issue
installation
Low-Priority
performance
Planned
platform: cross-platform
platform: windows
Potential Bug
Potential Bug
pull-request
question
refactor
Release
stale
User Support
V1
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/desktop#523
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Freedomwait on GitHub (May 14, 2026).
Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1721
App Version
Expected Behavior
start success
Actual Behavior
always starting server but can not finish
Steps to Reproduce
Debug Logs
Browser Logs
No response
Settings JSON
No response
Other
No response
┆Issue is synchronized with this Notion page by Unito
@dosubot[bot] commented on GitHub (May 14, 2026):
Hi @Freedomwait! I'm Dosu and I’m helping the desktop team.
This is a confirmed bug in v0.9.1 on macOS. The app gets stuck on "Starting Server" because the new asset autoscanning feature (introduced in this version) tries to initialize a SQLite database at a read-only location inside the
.appbundle (/Applications/ComfyUI.app/Contents/Resources/ComfyUI/user/comfyui.db) [1].The startup sequence fails like this:
/object_infoendpoint triggersseed_assets(["models"]).appbundle)/object_infoto succeedEarlier versions didn't have this problem because they didn't perform asset scanning during server initialization [1].
Workaround: You can try configuring the app to use a writable
--user-directoryor--database-urlpath via theComfy.Server.LaunchArgssetting in the Desktop app's config [1]. However, a proper fix should come from the team to ensure the default database path resolves to a writable location on macOS.To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.