Hello. With the help of my tutor Phil Archer I have coded an endless- loop pd-patch which is playing randomly a movie clip out of 50 different Quicktime-films, selecting a new random clip one after each other, playing the film fullscreen. The coding is working very well (attached picture) but there is a problem with the stability: the application is regularly crashing after about 4 to 5 minutes.
I donÂ’t know the reason, but I had a look at the activity window and there I could watch this: pd itself is increasing the physical storage... starting at about 70mb and getting bigger and bigger a new clip is chosen. When it reaches about 210 - 220mb after 4 or 5 minutes, the app crashes.
--
The Report says:
Process: pd [504] Path: /Users/hml/Desktop/Channels_TV.app/Contents/Resources/Scripts/../bin/pd Identifier: pd Version: ??? (???) Code Type: X86 (Native) Parent Process: Pd-extended [501]
Date/Time: 2010-06-14 09:05:46.112 +0200 OS Version: Mac OS X 10.6.3 (10D573) Report Version: 6
Interval Since Last Report: 104758 sec Crashes Since Last Report: 18 Per-App Crashes Since Last Report: 16 Anonymous UUID: DB66E35A-AF9A-41C8-AC29-6923433D8B95
Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000010 Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 org.perian.Perian 0x188aa92c decode_nal_units + 1228
(...)
Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00000010 ebx: 0x00000004 ecx: 0x00000000 edx: 0x00000010 edi: 0x1a8cc000 esi: 0x00000000 ebp: 0xbfffce18 esp: 0xbfffc800 ss: 0x0000001f efl: 0x00010246 eip: 0x188b792c cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0x00000010
--
...and loads of other stuff.
I am runninng this app on my Mac Book Pro: 3,06 GHz, Intel Core 2 Duo, 8 GB 1067 MHz DDR3, Graphics: NVIDIA GeForce 9600M with Pd version 0.41.4, GEM: ver: 0.91.3 ‘tigital’
The Quicktime films are compressed with the animation codec, without sound, ratio: 1680 x 1050, playing fullscreen. But size-wise the biggest film is not more then 15mb; most of the films are less then 1mb.
Any ideas what the problem could be?
Thanks a lot and greetings from Germany, Henning
The crash is with Perian - a third party set of codecs for Quicktime. Try converting the clips to a codec like Photo-JPEG or Apple Intermediate and see if that helps.
On Mon, Jun 14, 2010 at 3:15 AM, henning m. lederer | visual communication & animation henning@led-r-r.net wrote:
Hello. With the help of my tutor Phil Archer I have coded an endless- loop pd-patch which is playing randomly a movie clip out of 50 different Quicktime-films, selecting a new random clip one after each other, playing the film fullscreen. The coding is working very well (attached picture) but there is a problem with the stability: the application is regularly crashing after about 4 to 5 minutes.
I don’t know the reason, but I had a look at the activity window and there I could watch this: pd itself is increasing the physical storage... starting at about 70mb and getting bigger and bigger a new clip is chosen. When it reaches about 210 - 220mb after 4 or 5 minutes, the app crashes.
--
The Report says:
Process: pd [504] Path: /Users/hml/Desktop/Channels_TV.app/Contents/Resources/Scripts/../bin/pd Identifier: pd Version: ??? (???) Code Type: X86 (Native) Parent Process: Pd-extended [501]
Date/Time: 2010-06-14 09:05:46.112 +0200 OS Version: Mac OS X 10.6.3 (10D573) Report Version: 6
Interval Since Last Report: 104758 sec Crashes Since Last Report: 18 Per-App Crashes Since Last Report: 16 Anonymous UUID: DB66E35A-AF9A-41C8-AC29-6923433D8B95
Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000010 Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 org.perian.Perian 0x188aa92c decode_nal_units + 1228
(...)
Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00000010 ebx: 0x00000004 ecx: 0x00000000 edx: 0x00000010 edi: 0x1a8cc000 esi: 0x00000000 ebp: 0xbfffce18 esp: 0xbfffc800 ss: 0x0000001f efl: 0x00010246 eip: 0x188b792c cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0x00000010
--
...and loads of other stuff.
I am runninng this app on my Mac Book Pro: 3,06 GHz, Intel Core 2 Duo, 8 GB 1067 MHz DDR3, Graphics: NVIDIA GeForce 9600M with Pd version 0.41.4, GEM: ver: 0.91.3 ‘tigital’
The Quicktime films are compressed with the animation codec, without sound, ratio: 1680 x 1050, playing fullscreen. But size-wise the biggest film is not more then 15mb; most of the films are less then 1mb.
Any ideas what the problem could be?
Thanks a lot and greetings from Germany, Henning --
/// henning m. lederer /// visual communication& animation
/// master of digital arts /// diplom-designer [fh]
/// +44 (0)7551 960 327 (uk) /// +49 (0)179 572 38 13 (germany)
/// www.led-r-r.net /// henning@led-r-r.net
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hi Chris. Thanks a lot for your ideas. I gave it a try and Apple Intermediate and PhotoJpeg are definitely better. I didn't know that the Animation codec is using Perian. Okay: The current running time is now about 2 til 3 hours! The CPU is at about 40% Â… But it crashed again. The Physical Memory and the Virtual Memory (sorry, I used a wrong translation before) are still increasingÂ… slowly, but steady. When it reaches more or less 3 GB (2,98 GB physical memory) and about 4 GB (3,95 GB virtual memory) the app crashes again. This time completely with no report at all.
Is there any way to empty this cache within pd? Or why is it doing that at all?
Any help would be great! Thanks a lot so far.
Henning
--
On 14.06.10 13:56, chris clepper wrote:
The crash is with Perian - a third party set of codecs for Quicktime.
Try converting the clips to a codec like Photo-JPEG or Apple Intermediate and see if that helps.On Mon, Jun 14, 2010 at 3:15 AM, henning m. lederer | visual communication & animation <henning@led-r-r.net mailto:henning@led-r-r.net> wrote:
Hello. With the help of my tutor Phil Archer I have coded an endless- loop pd-patch which is playing randomly a movie clip out of 50 different Quicktime-films, selecting a new random clip one after each other, playing the film fullscreen. The coding is working very well (attached picture) but there is a problem with the stability: the application is regularly crashing after about 4 to 5 minutes. I don’t know the reason, but I had a look at the activity window and there I could watch this: pd itself is increasing the physical storage... starting at about 70mb and getting bigger and bigger a new clip is chosen. When it reaches about 210 - 220mb after 4 or 5 minutes, the app crashes. -- The Report says: Process: pd [504] Path: /Users/hml/Desktop/Channels_TV.app/Contents/Resources/Scripts/../bin/pd Identifier: pd Version: ??? (???) Code Type: X86 (Native) Parent Process: Pd-extended [501] Date/Time: 2010-06-14 09:05:46.112 +0200 OS Version: Mac OS X 10.6.3 (10D573) Report Version: 6 Interval Since Last Report: 104758 sec Crashes Since Last Report: 18 Per-App Crashes Since Last Report: 16 Anonymous UUID: DB66E35A-AF9A-41C8-AC29-6923433D8B95 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000010 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 org.perian.Perian 0x188aa92c decode_nal_units + 1228 (...) Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00000010 ebx: 0x00000004 ecx: 0x00000000 edx: 0x00000010 edi: 0x1a8cc000 esi: 0x00000000 ebp: 0xbfffce18 esp: 0xbfffc800 ss: 0x0000001f efl: 0x00010246 eip: 0x188b792c cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0x00000010 -- ...and loads of other stuff. I am runninng this app on my Mac Book Pro: 3,06 GHz, Intel Core 2 Duo, 8 GB 1067 MHz DDR3, Graphics: NVIDIA GeForce 9600M with Pd version 0.41.4, GEM: ver: 0.91.3 ‘tigital’ The Quicktime films are compressed with the animation codec, without sound, ratio: 1680 x 1050, playing fullscreen. But size-wise the biggest film is not more then 15mb; most of the films are less then 1mb. Any ideas what the problem could be? Thanks a lot and greetings from Germany, Henning
-
chris clepper -
henning m. lederer | visual communication & animation