[MacPorts] #16701: port upgrade installed memory not releasing (PPC)
#16701: port upgrade installed memory not releasing (PPC) --------------------------------+------------------------------------------- Reporter: artrigue@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: High | Milestone: Port Bugs Component: base | Version: 1.6.0 Keywords: | Port: --------------------------------+------------------------------------------- with -d I don´t see anything particular going on, it just keeps running until suddenly it stops: {{{ DEBUG: epoch: in tree: 0 installed: 0 DEBUG: nspr 4.7_1 exists in the ports tree DEBUG: nspr 4.7_1 is installed DEBUG: No need to upgrade! nspr 4.7_1 >= nspr 4.7_1 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/databases/db46 tclsh(6113,0xa000ed88) malloc: *** vm_allocate(size=475136) failed (error code=3) tclsh(6113,0xa000ed88) malloc: *** error: can't allocate region tclsh(6113,0xa000ed88) malloc: *** set a breakpoint in szone_error to debug unable to alloc 471346 bytes }}} The thing is, watching my memory usage, with istat widget, while it runs, it looks like no memory is being used at all until suddenly, it spikes. (this takes a while, I just check in every 15 minutes) Its not a slow rampup on the graph, it is flat until it spikes. Another thing, I just want to check because its big, look at that malloc. Does it request half a meg each port, just to verify port versions? {{{ sudo port selfupdate Password for admin: MacPorts base version 1.600 installed Downloaded MacPorts base version 1.600 The MacPorts installation is not outdated and so was not updated selfupdate done! }}} I tried tcl just at 8.5.4 and with the +memdebug +threads ... just hoping that might be the issue. -- Ticket URL: <http://trac.macports.org/ticket/16701> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16701: port upgrade installed memory not releasing (PPC) ---------------------------------+------------------------------------------ Reporter: artrigue@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: | Keywords: Port: | ---------------------------------+------------------------------------------ Changes (by jmr@macports.org): * cc: artrigue@gmail.com (removed) * priority: High => Normal * milestone: Port Bugs => MacPorts base bugs Comment: Port(1) always runs with /usr/bin/tclsh, so it's not going to be using Tcl 8.5.4 without some hackery. -- Ticket URL: <http://trac.macports.org/ticket/16701#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16701: port upgrade installed memory not releasing (PPC) ---------------------------------+------------------------------------------ Reporter: artrigue@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: | Keywords: Port: | ---------------------------------+------------------------------------------ Comment(by artrigue@gmail.com): hmmm, well I posted that bit because I had just read a previous ticket with memory issues with port where someone suggested updating tcl to 8.5.4 and trying again.. and the submitter responded that it worked. Do you know how I can check the tclsh version in /usr/bin ..? To late tonight for me to fidget with it, maybe tomorrow :) -- Ticket URL: <http://trac.macports.org/ticket/16701#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16701: port upgrade installed memory not releasing (PPC) ---------------------------------+------------------------------------------ Reporter: artrigue@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: | Keywords: Port: | ---------------------------------+------------------------------------------ Comment(by blb@macports.org): Using {{{ echo 'puts $tcl_patchLevel' | /usr/bin/tclsh }}} should tell you Tcl's version (8.4.7 if you're on 10.5). Note that the +memdebug is really only useful for actually tracking down memory issues. After having tried to use it some with port, and having it generate many, many megs of output, I put it on the back burner. -- Ticket URL: <http://trac.macports.org/ticket/16701#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16701: port upgrade installed memory not releasing (PPC) ---------------------------------+------------------------------------------ Reporter: artrigue@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: | Keywords: Port: | ---------------------------------+------------------------------------------ Comment(by artrigue@gmail.com): Replying to [comment:3 blb@…] I did have a 8.4 release ... although this is 10.4.11. I have rerun it with the tcl I´d gotten from ports, but it looks to have the same issue, with maybe one and a half gigs of ram tied up right now. It hasnt spiked quite as fast on the graphic... that makes me think I just didnt view the memory chart often enough last time: it does only update while you are watching it — kinda a useful feature. Thank you for the insight on memdebug, I´ll remove that! -- Ticket URL: <http://trac.macports.org/ticket/16701#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16701: port upgrade installed memory not releasing (PPC) ---------------------------------+------------------------------------------ Reporter: artrigue@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts Future Component: base | Version: 1.6.0 Resolution: duplicate | Keywords: Port: | ---------------------------------+------------------------------------------ Changes (by jmr@…): * status: new => closed * resolution: => duplicate Comment: Duplicate of #12022. -- Ticket URL: <http://trac.macports.org/ticket/16701#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts