[Bug]: Stuck searching for nodes

[visaeon]

Frontend Version

latest comfy commit

Expected Behavior

Double click presents all nodes

Actual Behavior

double click just shows a search bar and does not display anything

Steps to Reproduce

Im not sure how to reproduce it on another machine

Debug Logs

Nothing to note in terminal logs relating to the issue

Browser Logs

TypeError: nodeSearchService is undefined
setup NodeSearchFilter.vue:53
createHook runtime-core.esm-bundler.js:1808
callWithErrorHandling runtime-core.esm-bundler.js:195
callWithAsyncErrorHandling runtime-core.esm-bundler.js:202
__weh runtime-core.esm-bundler.js:1788
flushPostFlushCbs runtime-core.esm-bundler.js:379
flushJobs runtime-core.esm-bundler.js:415
flushJobs runtime-core.esm-bundler.js:419
promise callbackqueueFlush runtime-core.esm-bundler.js:319
queueJob runtime-core.esm-bundler.js:313
effect runtime-core.esm-bundler.js:5258
resetScheduling reactivity.esm-bundler.js:262
triggerEffects reactivity.esm-bundler.js:306
triggerRefValue reactivity.esm-bundler.js:1071
set value reactivity.esm-bundler.js:1118
canvasEventHandler NodeSearchBoxPopover.vue:132
processMouseDown litegraph.es.js:4532
processMouseDown changeTracker.ts:176
processMouseDown simpleTouchSupport.ts:102
processMouseDown rgthree.js:224
processMouseDown app.ts:1200
runtime-core.esm-bundler.js:270:12
TypeError: useNodeDefStore().nodeSearchService is undefined
search3 NodeSearchBox.vue:103
0 index-D8Zp4vRl.js:70915
callWithErrorHandling runtime-core.esm-bundler.js:195
callWithAsyncErrorHandling runtime-core.esm-bundler.js:202
emit runtime-core.esm-bundler.js:726
search2 index.mjs:826
onFocus4 index.mjs:339
0 index.mjs:1132
callWithErrorHandling runtime-core.esm-bundler.js:195
callWithAsyncErrorHandling runtime-core.esm-bundler.js:202
invoker runtime-dom.esm-bundler.js:693
reFocusInput NodeSearchBox.vue:121
createHook runtime-core.esm-bundler.js:1808
callWithErrorHandling runtime-core.esm-bundler.js:195
callWithAsyncErrorHandling runtime-core.esm-bundler.js:202
__weh runtime-core.esm-bundler.js:1788
flushPostFlushCbs runtime-core.esm-bundler.js:379
flushJobs runtime-core.esm-bundler.js:415
flushJobs runtime-core.esm-bundler.js:419
promise callbackqueueFlush runtime-core.esm-bundler.js:319
queueJob runtime-core.esm-bundler.js:313
effect runtime-core.esm-bundler.js:5258
resetScheduling reactivity.esm-bundler.js:262
triggerEffects reactivity.esm-bundler.js:306
triggerRefValue reactivity.esm-bundler.js:1071
set value reactivity.esm-bundler.js:1118
canvasEventHandler NodeSearchBoxPopover.vue:132
processMouseDown litegraph.es.js:4532
processMouseDown changeTracker.ts:176
processMouseDown simpleTouchSupport.ts:102
processMouseDown rgthree.js:224
processMouseDown app.ts:1200
runtime-core.esm-bundler.js:270:12
Source map error: request failed with status 404
Resource URL: http://127.0.0.1:8188/extensions/ComfyUI_smZNodes/js/exif.js
Source Map URL: /sm/4f4f84956292156efc04b79e1131dc7c3a51794b7b3d62b43ed5eaca1b36d71e.map
Source map error: request failed with status 404
Resource URL: http://127.0.0.1:8188/kjweb_async/purify.min.js
Source Map URL: purify.min.js.map
Source map error: request failed with status 404
Resource URL: http://127.0.0.1:8188/extensions/comfy_mtb/extern/shodown.min.js
Source Map URL: showdown.min.js.map
Source map error: request failed with status 404
Resource URL: http://127.0.0.1:8188/extensions/comfy_mtb/extern/dom-purify.js
Source Map URL: purify.min.js.map
unreachable code after return statement Reflect.js:897:21
unreachable code after return statement Reflect.js:1029:21
unreachable code after return statement Reflect.js:1288:21
unreachable code after return statement Reflect.js:1354:21
The connection to ws://127.0.0.1:8188/ws was interrupted while the page was loading. api.ts:108:18
Firefox can’t establish a connection to the server at ws://127.0.0.1:8188/ws?clientId=c80b6c955c2a43ea93ae6e04dd494969. api.ts:108:18
Firefox can’t establish a connection to the server at ws://127.0.0.1:8188/ws?clientId=c80b6c955c2a43ea93ae6e04dd494969. api.ts:108:18
Firefox can’t establish a connection to the server at ws://127.0.0.1:8188/ws?clientId=c80b6c955c2a43ea93ae6e04dd494969. api.ts:108:18
Firefox can’t establish a connection to the server at ws://127.0.0.1:8188/ws?clientId=c80b6c955c2a43ea93ae6e04dd494969. api.ts:108:18

What browsers do you use to access the UI ?

Mozilla Firefox

Other

No response

[huchenlei]

Please follow the instruction in bug report to disable all custom nodes and reopen if the issue persists.

• 3: You confirmed that the bug is not caused by a custom node. You can disable all custom nodes by passing
  --disable-all-custom-nodes command line argument.

[visaeon]

The problem is solved when i disable all nodes. But as soon as i add a node such as manager the problem returns.
Ive spent hours trying to resolve it using chat gpt and claude but i cant seem to narrow down the problem,

I have tried several browsers, also a new version of comfy.

Im happy to provide any information that you may find helpfull

[huchenlei]

The problem is solved when i disable all nodes. But as soon as i add a node such as manager the problem returns. Ive spent hours trying to resolve it using chat gpt and claude but i cant seem to narrow down the problem,

I have tried several browsers, also a new version of comfy.

Im happy to provide any information that you may find helpfull

So you can reproduce this issue with ComfyUI core + ComfyUI manager alone?

[visaeon]

The issue for me was
ComfyUI_NestedNodeBuilder. I removed it, and everything is fine now.

You can now close this as solved

[gonzalu]

I do not have NestedNodeBuilder installed but, problem exists for me. I have a lot of custom nodes installed. Not sure if I can figure out which one might be causing the issue without a lot of work. Hopefully there is a way to debug this in a way that can find the culprit without re-installing each one at a time :(

Thank you all.

[huchenlei]

I do not have NestedNodeBuilder installed but, problem exists for me. I have a lot of custom nodes installed. Not sure if I can figure out which one might be causing the issue without a lot of work. Hopefully there is a way to debug this in a way that can find the culprit without re-installing each one at a time :(

Thank you all.

ComfyCLI has a bisect feature that can help you locate culprit custom node: https://github.com/Comfy-Org/comfy-cli#bisect-custom-nodes

[gonzalu]

I do not have NestedNodeBuilder installed but, problem exists for me. I have a lot of custom nodes installed. Not sure if I can figure out which one might be causing the issue without a lot of work. Hopefully there is a way to debug this in a way that can find the culprit without re-installing each one at a time :(
Thank you all.

ComfyCLI has a bisect feature that can help you locate culprit custom node: https://github.com/Comfy-Org/comfy-cli#bisect-custom-nodes

How do I use it? I am sorry I can;t figure it out... do I just run

$comfy blah blah

??

[huchenlei]

I do not have NestedNodeBuilder installed but, problem exists for me. I have a lot of custom nodes installed. Not sure if I can figure out which one might be causing the issue without a lot of work. Hopefully there is a way to debug this in a way that can find the culprit without re-installing each one at a time :(
Thank you all.

ComfyCLI has a bisect feature that can help you locate culprit custom node: https://github.com/Comfy-Org/comfy-cli#bisect-custom-nodes

How do I use it? I am sorry I can;t figure it out... do I just run

$comfy blah blah

??

Install it first by pip install comfy-cli (ref: https://github.com/Comfy-Org/comfy-cli#installation)

[gonzalu]

Thank you, I have it installed when I added my custom nodes to the registry.

So, just use it as that? While comfy is running or not?

[gonzalu]

OK, the bisect did not find anything that was causing it... will ALL NODES disabled, it is still there. So, it is MANAGER.

If I disable the MANAGER, the problem goes away...

[christian-byrne]

OK, the bisect did not find anything that was causing it... will ALL NODES disabled, it is still there. So, it is MANAGER.

If I disable the MANAGER, the problem goes away...

Did you try updating or reinstalling the manager? You should post browser logs.