[PD-dev] [ pure-data-Bugs-1845770 ] PiDiP ascii renderer eats mac hard disks
SourceForge.net
noreply at sourceforge.net
Sun May 11 15:45:45 CEST 2008
Bugs item #1845770, was opened at 2007-12-06 15:15
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1845770&group_id=55736
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: pd-extended
Group: None
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: stereopticon (stereopticon)
Assigned to: Nobody/Anonymous (nobody)
Summary: PiDiP ascii renderer eats mac hard disks
Initial Comment:
...iknow, it sounds like a tabloid headline.
I'm running OSX 10.4.11 on a Macbook Pro 2.16 GHz Intel Core 2 Duo. I upgraded to pd 0.39.3-extended-rc5 recently and began messing around with the PiDiP ascii renderer. Early in a day of testing I loaded an 11-second, 640x480 quicktime clip compressed with the H.264 codec into pdp_ascii-help.pd and gotâ¦nothing. The patch became completely unresponsive to mouse clicks and I ended up having to quit and relaunch pd and X11. I eventually discovered that pdp_ascii works with the Sorenson video 3 codec and spent a happy hour turning bits of things into ascii art.
Then I noticed something strange. The hard drive was nearly full. As I watched in shock, it filled up completely. A couple of minutes of searching found the culprit: my console log file for the session was 36 gigs. Turns out that all that space was taken up by a single message, âskipping corrupted frameâ, spit out over and over again at the ridiculous rate of 4 megs/sec. Trying to load the H.264 quicktime is what initiated the loop. Iâve been able to replicate it and came up with the following info: the bug runs independent of pd and X11, hogs 80% of the CPU, and since for some reason the process is tied to the OSX loginwindow process I was only able to kill it by logging out.
Cheers,
Michael
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2008-05-11 09:45
Message:
Logged In: YES
user_id=27104
Originator: NO
Is this still a problem on 0.40.3-extended test releases? It is
reproducable?
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2008-04-07 05:40
Message:
Logged In: YES
user_id=564396
Originator: NO
stupid me, but is the console log file part of os-x, pd-extended or did
you add it manually?
(imho, writing things (even if there are lots of things) to the console
does not really qualify as a bug)
furthermore, the log-message is likely not being emitted by pidip, but
rather by the underlying decoding library (libquicktime);
so the bug report should probably go there instead of here
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1845770&group_id=55736
More information about the Pd-dev
mailing list