Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Perform replace from Find in Files with multiple instances open causes program to crash/disappear #5680

Open
LouieTian0209 opened this issue Sep 5, 2024 · 5 comments

Comments

@LouieTian0209
Copy link

Version: Linux gtk2

Steps to reproduce:

  1. Open 2 instances of CudaText
  2. On 2nd instance, perform some search in Find in Files dialog
  3. Open Replace dialog from menu button
  4. Enter some replacement text, and click Replace

Current Behavior:
2nd instance crashed/disappeared, 1st instance is in tact

Expected Behavior:
Replacement should be completed on 2nd instance and both instances should stay open after the replacement.

@Alexey-T
Copy link
Owner

Alexey-T commented Sep 5, 2024

  1. FIF4 crashes? then show me the COnsole panel log with error. or Cud crashes? how? run Cud from terminal, show terminal text.
  2. I cannot repro this yet. I dont get idea - how 2nd running Cud instance can affect another instance? it cannot. your steps are not exact, seems. tell me what you do in BOTH Cud instances.

@Alexey-T
Copy link
Owner

Alexey-T commented Sep 5, 2024

1b. if Cud crashes and terminal text is very poor, take the new beta (linux-qt5) with .dbg file. it will show more extended text in terminal.
#5633 (comment)

@LouieTian0209
Copy link
Author

1b. if Cud crashes and terminal text is very poor, take the new beta (linux-qt5) with .dbg file. it will show more extended text in terminal. #5633 (comment)

Hmm... interesting. Tried with this qt5 version and didn't encounter this issue.

The original issue was that when performing Replace on 2nd instance, the entire 2nd instance just crashes/disappears, while the 1st instance is not being affected at all.

I'll try again later with the gtk2 version and try to capture any log info from terminal.

@Alexey-T
Copy link
Owner

Alexey-T commented Sep 5, 2024

So it is FIF4 who crashes, not Cud crashes. ok. I cannot repro it on gtk2 version too. maybe I need some fixed actions with fixed files.

waiting for the Console crash log.

@LouieTian0209
Copy link
Author

This is interesting... tried the qt5 version with dbg and cannot trigger this issue. Tried again a few times with my installed gtk2 version and cannot trigger the issue either.

But judging from the behavior I suspect it's the same root cause as #5688

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants