[MacPorts] #49121: Exiting tmux causes high notifyd CPU usage on El Capitan
#49121: Exiting tmux causes high notifyd CPU usage on El Capitan -------------------------+-------------------------------- Reporter: hotpxless@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: -------------------------+-------------------------------- If I let tmux run for some time (half hour) and then exit (not just detaching), it will cause 100% notifyd CPU usage on El Capitan and freezes the whole system. -- Ticket URL: <https://trac.macports.org/ticket/49121> MacPorts <https://www.macports.org/> Ports system for OS X
#49121: Exiting tmux causes high notifyd CPU usage on El Capitan --------------------------+-------------------------------- Reporter: hotpxless@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by hotpxless@…): Sorry should have set Port to tmux... Don't know how to change it. -- Ticket URL: <https://trac.macports.org/ticket/49121#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#49121: Exiting tmux causes high notifyd CPU usage on El Capitan --------------------------+------------------------ Reporter: hotpxless@… | Owner: tessarek@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: elcapitan Port: tmux | --------------------------+------------------------ Changes (by ryandesign@…): * owner: macports-tickets@… => tessarek@… * keywords: => elcapitan * port: => tmux Comment: Check if the tmux-devel port has the same problem. That uses a newer development version of tmux from July. -- Ticket URL: <https://trac.macports.org/ticket/49121#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#49121: Exiting tmux causes high notifyd CPU usage on El Capitan --------------------------+------------------------ Reporter: hotpxless@… | Owner: tessarek@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: elcapitan Port: tmux | --------------------------+------------------------ Comment (by hotpxless@…): Replying to [comment:2 ryandesign@…]:
Check if the tmux-devel port has the same problem. That uses a newer development version of tmux from July.
Problem still exists with tmux-devel. -- Ticket URL: <https://trac.macports.org/ticket/49121#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#49121: Exiting tmux causes high notifyd CPU usage on El Capitan --------------------------+------------------------ Reporter: hotpxless@… | Owner: tessarek@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: elcapitan Port: tmux | --------------------------+------------------------ Comment (by tessarek@…): Hi Ryan. I've updated the Portfile to build from the latest commit point for tmux- devel. -- Ticket URL: <https://trac.macports.org/ticket/49121#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
#49121: Exiting tmux causes high notifyd CPU usage on El Capitan --------------------------+------------------------ Reporter: hotpxless@… | Owner: tessarek@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: elcapitan Port: tmux | --------------------------+------------------------ Comment (by tessarek@…): If this latest code has the same problem on El-Capitan, the OP has to open a ticket on tmux mailing list or group (https://groups.google.com/forum/#!forum/tmux-users). -- Ticket URL: <https://trac.macports.org/ticket/49121#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
#49121: Exiting tmux causes high notifyd CPU usage on El Capitan --------------------------+------------------------ Reporter: hotpxless@… | Owner: tessarek@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: elcapitan Port: tmux | --------------------------+------------------------ Comment (by tessarek@…): Ryan, do you want me to open a separate defect for the tmux portfile update? -- Ticket URL: <https://trac.macports.org/ticket/49121#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X
#49121: Exiting tmux causes high notifyd CPU usage on El Capitan --------------------------+------------------------ Reporter: hotpxless@… | Owner: tessarek@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: elcapitan Port: tmux | --------------------------+------------------------ Comment (by hotpxless@…): Replying to [comment:4 tessarek@…]:
Hi Ryan.
I've updated the Portfile to build from the latest commit point for tmux-devel.
Hi, How should I update my tmux-devel to the new version? On macports it's still the july one -- Ticket URL: <https://trac.macports.org/ticket/49121#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X
#49121: Exiting tmux causes high notifyd CPU usage on El Capitan --------------------------+------------------------ Reporter: hotpxless@… | Owner: tessarek@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: elcapitan Port: tmux | --------------------------+------------------------ Comment (by tessarek@…): Replying to [comment:7 hotpxless@…]:
How should I update my tmux-devel to the new version? On macports it's still the july one
You can either wait until Ryan will have updated the Portfile on the global repo. Or you could use a local repository as described in the documentation. For testing purposes you can download a compiled binary at https://evermeet.cx/pub/macosx/tmux-devel/tmux [[BR]] Please note that it was compiled within the macports environment on Mac OS X 10.9.5. -- Ticket URL: <https://trac.macports.org/ticket/49121#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X
#49121: Exiting tmux causes high notifyd CPU usage on El Capitan --------------------------+------------------------ Reporter: hotpxless@… | Owner: tessarek@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: elcapitan Port: tmux | --------------------------+------------------------ Comment (by hotpxless@…): Replying to [comment:8 tessarek@…]:
Replying to [comment:7 hotpxless@…]:
How should I update my tmux-devel to the new version? On macports it's still the july one
You can either wait until Ryan will have updated the Portfile on the global repo. Or you could use a local repository as described in the documentation.
For testing purposes you can download a compiled binary at https://evermeet.cx/pub/macosx/tmux-devel/tmux [[BR]] Please note that it was compiled within the macports environment on Mac OS X 10.9.5.
Hi. I went ahead and compiled a GitHub (https://github.com/tmux/tmux) version of hash 7120ab2. Everything works fine now. Could you update it to the latest github version? -- Ticket URL: <https://trac.macports.org/ticket/49121#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X
#49121: Exiting tmux causes high notifyd CPU usage on El Capitan --------------------------+------------------------ Reporter: hotpxless@… | Owner: tessarek@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: elcapitan Port: tmux | --------------------------+------------------------ Comment (by tessarek@…): Replying to [comment:9 hotpxless@…]:
Hi. I went ahead and compiled a GitHub (https://github.com/tmux/tmux) version of hash 7120ab2. Everything works fine now. Could you update it to the latest github version?
That's the binary I sent you the link to. It is the version of hash 7120ab2. In any case, I have updated the Portfile, but Ryan has to apply it, since I do not have write permission on the svn repo. Still not sure why git (plus gitolite for access) isn't used for MacPorts. That would make things so much easier. -- Ticket URL: <https://trac.macports.org/ticket/49121#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X
#49121: tmux @2.0: Exiting causes high notifyd CPU usage on El Capitan --------------------------+-------------------------------- Reporter: hotpxless@… | Owner: tessarek@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: elcapitan haspatch Port: tmux | --------------------------+-------------------------------- Changes (by ryandesign@…): * cc: ryandesign@… (added) * keywords: elcapitan => elcapitan haspatch Comment: Sorry, I didn't see the above messages because I was not Cc'd on this ticket. I've Cc'd myself now, and will apply the patch to the port. Note that when the version of a port is increased, its revision should be dropped to 0. Discussions about switching the MacPorts repository from Subversion to Git should occur on the macports-dev mailing list, not in a ticket. This discussion has occurred a number of times before; you may want to search the archives first to see what we talked about the last times it came up. -- Ticket URL: <https://trac.macports.org/ticket/49121#comment:11> MacPorts <https://www.macports.org/> Ports system for OS X
#49121: tmux @2.0: Exiting causes high notifyd CPU usage on El Capitan --------------------------+-------------------------------- Reporter: hotpxless@… | Owner: tessarek@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: elcapitan haspatch Port: tmux | --------------------------+-------------------------------- Changes (by ryandesign@…): * status: new => closed * resolution: => fixed Comment: Actually I am reminded now that the patch to update tmux-devel was already committed in #49173. The request to update the tmux port is #49364. -- Ticket URL: <https://trac.macports.org/ticket/49121#comment:12> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts