Hello all, Pd 0.51-1 does not want to quit on my Macbook Pro running Mojave 10.14.4. After several forcequitings Pd some Pd processes are shown on my activity monitor taking up to 80% of my CPU.
Any ideas?
Cheers,

@ultraman I have similar problems, having to force quit. Also the whole computer crashes when using Pd. 2011 Mac Book Pro with OSX High Sierra.

pd is composed of a gui process (which is a tcl/tk "wish" shell) and the "core" process that does all of the message/dsp processing (and some gui handling logic). The main "app" process is the gui/"wish" one so sometimes when that unexpectedly quits it leaves the "headless" process running.

I don't know why the gui is freezing, but that is why there are phantom pd processes. (Probably safest to force quit them all before attemting to restart pd)

If you look at your logs, are there any crash reports or anything?
(in the "User Reports")
also, are you using or loading any externals when this happens?

@seb-harmonik.ar Hi, yes I am killing the phantom processes every time.
There is no crashing reports and no loading at the time. Everything works, is just not leting me quit the program ever,

FWIW, a few days ago I was showing [vstplugin~] in a class, and it hung, and I could get control back only by rebooting. This was on Mac. Cmd-Q didn't do anything, and right-clicking on the Pd icon in the dock did not reveal a force-quit option. I haven't typically had that problem in Linux.

It doesn't normally happen for me in Mac, so my observation is maybe not the same as in the original post.

Come to think of it -- @ultraman, are there any particular objects that provoke this kind of hang? In my case it was very clearly an errant instance of a complex external (and an external which invokes third-party executables), but I've never seen this with plain vanilla objects.

hjh

@ultraman I have had the same problem in windows...... the Pd executable "orphaned" in the background.... when it has not successfully disconnected from the soundcard when closed.
As @seb-harmonik.ar says....... wish has closed, but not Pd.
Reopening Pd then fails as it cannot hook into the soundcard.
Particularly when starting Pd with command line switches that determine the audio settings for an ASIO device.
Had to kill the process in task manager..... which is presumably "force quit" on a Mac.
As @ddw_music I suspect a hook...... and 100% an audio hook to another program or driver.
David.

My problems seem to intensify when working with many graph-in-parent objects.

@ddw_music Hey, Nope, No particular obejcts or patches, and it happens pretty much everytime.

@ultraman any reason why you are still on 10.14.4? perhaps updating to the latest os (10.14.6) would help? (probably not but worth a shot imo)

I think I just got this on MacOS 10.14.6 on 0.51-2, I did notice a .diag file in the Console in System Reports from pd: (not sure if it's related)

Event:           wakeups
Action taken:    none
Wakeups:         45001 wakeups over the last 82 seconds (548 wakeups per second average), exceeding limit of 150 wakeups per second over 300 seconds
Wakeups limit:   45000
Limit duration:  300s
Wakeups caused:  45001
Duration:        18.10s
Steps:           4

and later:

Heaviest stack for the target process:
  3  usleep + 53 (libsystem_c.dylib + 501768) [0x7fff76eef808]
  2  __semwait_signal + 10 (libsystem_kernel.dylib + 20270) [0x7fff76f63f2e]

and later:

3  usleep + 53 (libsystem_c.dylib + 501768) [0x7fff76eef808]
    2  __semwait_signal + 10 (libsystem_kernel.dylib + 20270) [0x7fff76f63f2e]
      2  <Kernel mode>
    1  nanosleep + 29 (libsystem_c.dylib + 501866) [0x7fff76eef86a]
  1  pthread_mutex_lock + 42 (libsystem_pthread.dylib + 4449) [0x7fff7701d161]

might be time for a bug report.. gonna try to reproduce/narrow it down somehow..