Opened 7 years ago

Closed 7 years ago

#32156 closed defect (invalid)

port selfupdate freeze os x 10.7 dock

Reported by: fotak@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version: 2.0.3
Keywords: Cc:
Port:

Description (last modified by ryandesign (Ryan Schmidt))

I have big problem with Macports and OS X 10.7 if start port -d selfupdate command OS dock freez and it does not answer. Activity Monitor shows 100 - 260 % CPU load (4 core CPU). If kill dock process, it restart with CPU load > 300%. After the reloading OS CPU load > 300% (Leon thanks)

Solution for this problem:

cd $HOME/Library/Application Support/Dock
rm -rf *.db
killall Dock

and newer to start port selfupdate

it is extended on:

macports 2.0.3 & last svn version

osx =>10.7

I did not observe this problem on 10.6

Attachments (2)

Sample of Dock.txt (870.7 KB) - added by fotak@… 7 years ago.
Screen Shot 2011-11-20 at 11.36.23 PM.png (182.5 KB) - added by fotak@… 7 years ago.

Download all attachments as: .zip

Change History (5)

Changed 7 years ago by fotak@…

Attachment: Sample of Dock.txt added

Changed 7 years ago by fotak@…

comment:1 Changed 7 years ago by ryandesign (Ryan Schmidt)

Component: portsbase
Description: modified (diff)

I have no idea how MacPorts could be responsible for that.

comment:2 in reply to:  1 Changed 7 years ago by fotak@…

Replying to ryandesign@…:

I have no idea how MacPorts could be responsible for that.

OK, this is actual not MacPorts problem. Problem appears only if MacPorts installed in $HOME/Applications directory, I transferred MacPorts in /usr/local and it's ok now. This is Launchpad bug.

comment:3 Changed 7 years ago by ryandesign (Ryan Schmidt)

Resolution: invalid
Status: newclosed

I hope you mean /opt/local; It's very unsupported to have MacPorts in /usr/local, and its configure script won't even let you do that.

Note: See TracTickets for help on using tickets.