meld icon indicating copy to clipboard operation
meld copied to clipboard

Meld doesn't quit properly on Mojave 10.14.2

Open michalgutowski opened this issue 5 years ago • 11 comments

I've noticed that after closing Meld (cmd+q), its processes are still running - as a result it's not possible to open Meld app again. I can only open it again if I first kill two Meld related processes in the terminal.

This only happens when you actually compared some files or created a blank comparison. When you simply open Meld and quit it right away there is no issue. I'm running Meld 3.19.2 (r3).

michalgutowski avatar Dec 12 '18 18:12 michalgutowski

Same here, exactly same OS version and Meld version, exactly same issue.

yanli0303 avatar Dec 12 '18 19:12 yanli0303

I'll look into it this weekend. Thanks for the report.

yousseb avatar Dec 13 '18 15:12 yousseb

Please check on this build https://github.com/yousseb/meld/releases/tag/osx-13

yousseb avatar Dec 16 '18 07:12 yousseb

Looks better. With 3.19.2 (r4) I can re-launch Meld without problems. However I can still see Meld process running even after quitting:

$ ps -ef | grep -i [m]eld 501 32935 1 0 10:38AM ?? 0:00.02 /Applications/Meld.app/Contents/MacOS/Meld

To keep things nice and clean I should still kill that process manually.

michalgutowski avatar Dec 17 '18 09:12 michalgutowski

Humm.. Not sure what is happening at your end. I'm not getting this (I used to in the previous version). Going to be harder to debug..

yousseb avatar Dec 17 '18 15:12 yousseb

@yousseb This issue is gone on my machine, macOS Mojave 10.14.2 (18C54). Thanks for the quick fix!

yanli0303 avatar Dec 17 '18 15:12 yanli0303

@yousseb - try with these steps:

  1. open Meld
  2. check ps -ef - you will have one Meld process running
  3. crate blank file comparision
  4. check ps -ef - you will have two Meld processes running
  5. quit Meld
  6. check ps -ef - you will have one Meld process running

michalgutowski avatar Dec 17 '18 16:12 michalgutowski

Are you guys still getting this issue? If you are, give this build a shot. I'm unable to fully reproduce (sometimes it happens, but it hasn't occurred to me in a long while.) This build is hopefully better. https://github.com/yousseb/meld/releases/tag/osx-15

yousseb avatar Dec 25 '18 03:12 yousseb

Still happens to me. Opening Meld will spawn two meld processes and quitting just kills only one of them (the one that was created first, observation based on the pid)

nobodo avatar Apr 11 '19 09:04 nobodo

+1. This is still happening with 3.19.2 (r6) on macOS 10.14.5

huangw5 avatar Jul 18 '19 17:07 huangw5

This is still happening for me using Meld v3.19.2 on macOS 10.15.3.

I'm invoking Meld using git diff-tool and this config:

[difftool "meld"]
  cmd = open -W  -n -a Meld --args $(cd $(dirname \"$LOCAL\") && pwd)/$(basename \"$LOCAL\") $(cd $(dirname \"$REMOTE\") && pwd)/$(basename \"$REMOTE\")
  trustExitCode = true

I noticed that I can bypass the issue if I first close all Meld diffing instances with Command-W, and only then quit the Meld app with Command-Q. If I use Command-Q without closing all diffing instances (even after saving any changes), I find zombie Meld processes.

jtan189 avatar Apr 12 '20 15:04 jtan189