Opened 9 years ago
Closed 9 years ago
#49121 closed defect (fixed)
tmux @2.0: Exiting causes high notifyd CPU usage on El Capitan
Reported by: | hotpxl (Yutian Li) | Owned by: | tessus (Helmut K. C. Tessarek) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | elcapitan haspatch | Cc: | ryandesign (Ryan Carsten Schmidt) |
Port: | tmux |
Description
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.
Attachments (1)
Change History (13)
comment:1 Changed 9 years ago by hotpxl (Yutian Li)
comment:2 follow-up: 3 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | elcapitan added |
---|---|
Owner: | changed from macports-tickets@… to tessarek@… |
Port: | tmux added |
Check if the tmux-devel port has the same problem. That uses a newer development version of tmux from July.
comment:3 Changed 9 years ago by hotpxl (Yutian Li)
Replying to 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.
comment:4 follow-up: 7 Changed 9 years ago by tessus (Helmut K. C. Tessarek)
Hi Ryan.
I've updated the Portfile to build from the latest commit point for tmux-devel.
Changed 9 years ago by tessus (Helmut K. C. Tessarek)
Attachment: | Portfile-tmux.diff added |
---|
comment:5 Changed 9 years ago by tessus (Helmut K. C. 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).
comment:6 Changed 9 years ago by tessus (Helmut K. C. Tessarek)
Ryan, do you want me to open a separate defect for the tmux portfile update?
comment:7 follow-up: 8 Changed 9 years ago by hotpxl (Yutian Li)
Replying to 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
comment:8 follow-up: 9 Changed 9 years ago by tessus (Helmut K. C. Tessarek)
Replying to 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
Please note that it was compiled within the macports environment on Mac OS X 10.9.5.
comment:9 follow-up: 10 Changed 9 years ago by hotpxl (Yutian Li)
Replying to tessarek@…:
Replying to 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
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?
comment:10 Changed 9 years ago by tessus (Helmut K. C. Tessarek)
Replying to 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.
comment:11 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|---|
Keywords: | haspatch added |
Summary: | Exiting tmux causes high notifyd CPU usage on El Capitan → tmux @2.0: Exiting causes high notifyd CPU usage on El Capitan |
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.
comment:12 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Sorry should have set Port to tmux... Don't know how to change it.