BUG - Goto Anything freezes when

  • 1.0.201

  • Windows 10 64bit

When you use Goto Anything, it dynamically changes the results as you type. But if you enter a punctuation mark (e.g. . * !), the result list completely freezes. Even deleting and writing something else it no longer works. You have to exit the goto box and press Ctrl+G to make it work again.

Please report bugs on GitHub as we can’t track their status here.

1 Like

Done! https://github.com/laurent22/joplin/issues/3093

2 Likes

The Github issue was closed but in the last Joplin version 1.0.201 it still happens. I wrote here because the issue is locked

You had this bug in v1.0.201, so now you’ve tried v1.0.201 and you still have the bug. Is there something unexpected about this?

oh how stupid I am! I was sure it was the previous version. I’m sorry!

I'm suffering from similar bug in Joplin 1.0.227. GoTo dropdown freezes, no matter what I write.
Kubuntu 20.04

I use Go-to command frequently :sob:

However in 1.0.226 it behaves smoothly:

So, for my, 227 is totally unusable and I've restored 226.

Please provide the console log https://joplinapp.org/debugging

console.log only shows warnings:

/tmp/.mount_JoplinC1b7iT/resources/app.asar/gui/NoteEditor/utils/useMessageHandler.js:30 Got ipc-message: noteRenderComplete undefined


/tmp/.mount_JoplinC1b7iT/resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:11494 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Connect(Dialog), Connect(HelpButtonComponent)


/tmp/.mount_JoplinC1b7iT/resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:11494 Warning: componentWillUpdate has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

* Move data fetching code or side effects to componentDidUpdate.
* Rename componentWillUpdate to UNSAFE_componentWillUpdate to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Connect(Dialog), Connect(HelpButtonComponent)


Got ipc-message: noteRenderComplete undefined

I’ve also attached log.txt:
log.txt (4.4 KB)

i’ve tested pre-229 but it still has the bug.

It will be fixed in the next version

oh, thank you so much! :slight_smile: