• nico_demus

    So, I've got an older computer that I've been running a PD/GEM patch on for a number of years, and it's been consistently performing until recently when it began crashing once or twice a day. I seem to be getting the same sort of report from console and was wondering if anyone could shed some light on this while I try and sort this out.

    I keep getting this in every log for the most part, I can post more... nothing has been changed or updated recently, it's been kind of just a computer I have to test and run things on, so I'm confused to as where this new issue could be coming from....

    Thread 13 Crashed:
    0 ...pple.AppleIntermediateCodec 0x06c15cb8 get_band + 312
    1 ...pple.AppleIntermediateCodec 0x06c0b6cc decoder_entry(void*) + 428
    2 libSystem.B.dylib 0x9002b200 _pthread_body + 96

    Thread 14 Crashed:
    0 ...pple.AppleIntermediateCodec 0x06c15cb8 get_band + 312
    1 ...pple.AppleIntermediateCodec 0x06c0b6cc decoder_entry(void*) + 428
    2 libSystem.B.dylib 0x9002b200 _pthread_body + 96

    Thread 14 crashed with PPC Thread State 64:
    srr0: 0x0000000006c15cb8 srr1: 0x100000000200f030 vrsave: 0x0000000080000000
    cr: 0x44000048 xer: 0x0000000020000000 lr: 0x000000000000000a ctr: 0x00000000000000b4
    r0: 0x0000000000000000 r1: 0x00000000f068cd40 r2: 0x000000000001000c r3: 0x0000000008a1a000
    r4: 0x0000000000000020 r5: 0x00000000aec00000 r6: 0x000000000757b398 r7: 0x00000000ffff414f
    r8: 0x0000000000000001 r9: 0x000000000000000f r10: 0xffffffff0000bec1 r11: 0x00000000ffff414f
    r12: 0x00000000000caec0 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
    r16: 0x0000000000000000 r17: 0x0000000000000000 r18: 0x00000000ffff505b r19: 0x000000000000aec0
    r20: 0x00000000000c0000 r21: 0x00000000f068cd80 r22: 0x0000000000000240 r23: 0x0000000000000000
    r24: 0x000000000000000f r25: 0x00000000000c0000 r26: 0x0000000000000010 r27: 0x000000000757b380
    r28: 0x0000000000000000 r29: 0x00000000000000c0 r30: 0x0000000000000020 r31: 0x0000000006c15ba0

    thanks in advance,

    N

    posted in technical issues read more
  • nico_demus

    Hi, I've begun the compiling process and I've run into an issue when attempting to install that in Error 1 (ignored) messages being produced when trying to install nonCVS files etc.

    PD-Extended will run after the compilation ends (following these errors) and while it runs (it would appear) I am having errors with certain objects like pix_filmQT being unable to locate video files.

    Any idea where I went wrong? I've spent most of the day walking through the process and was hoping to have some level of resolution.

    Nico

    posted in technical issues read more
  • nico_demus

    Hello Everyone.

    So, I'm attempting to run PD/Gem on a 10.5.6 leopard mac and have run into issues that may or may not have to do with the computer being 64 bit and PD Extended 0.41.4 being 32 bit.... is anyone out there running it successfully with video and GL? Is there a 64 bit version of PD extended for Intel Mac that I'm just totally overlooking? I'm basically having malloc errors crash the program after running normally without jumps in CPU etc.

    N

    posted in technical issues read more
  • nico_demus

    Hi...

    I'm currently looking at PD-Extended 0.41.4 not being able to handle playing back 1920 x 1080 video files. My patch is hyper-simple.... just loading two layers of 1920 x 1080 HD video files... switching videos in and out as they play using a shell command. unfortunately this process needs to continue stably for longer than a few hours (which is all I've got right now).... When I let things run, PD crashes and I get the following error in Console.

    8/25/09 1:38:48 PM [0x0-0x18018].org.puredata.pd.wish[271] pd(272,0xa03ce720) malloc: *** mmap(size=4149248) failed (error code=12)
    8/25/09 1:38:48 PM [0x0-0x18018].org.puredata.pd.wish[271] *** error: can't allocate region
    8/25/09 1:38:48 PM [0x0-0x18018].org.puredata.pd.wish[271] *** set a breakpoint in malloc_error_break to debug
    8/25/09 1:38:48 PM [0x0-0x18018].org.puredata.pd.wish[271] terminate called after throwing an instance of 'std::bad_alloc'

    Any ideas? Thoughts? I'm not currently on the computer with the patch, but I can post sample content that is causing this crash later.... This is happening on a quad core Intel-Xeon Mac with 4 GB of memory.

    Memory allocation and Malloc is an area where I'm less than confident and would great appreciate some insight into why this is going on.... or may be going on.

    Thanks!

    posted in technical issues read more
  • nico_demus

    Hi All,

    I've been running into an issue with a piece that has been running normally on Tiger for several years. Unfortunately the machine had to have the OS reinstalled and Apple went ahead and upgraded the system to Leopard and unfortunately I'm without the re-install discs to step back to Tiger.

    So, I upgraded the PD/GEM version to 0.40.03 extended in order to get the piece to run but unfortunately this new crashing issue is occurring.

    The piece is designed to record, save and playback video files and do so automatically when the patch is open. I'm using "pix_video" to record files.... If I delete "pix_video" there is no issue, but with pix_video in the patch, the error occurs and PD crashes within ten seconds of opening.

    Is anyone else running into this? Any solutions/comments/diatribes?

    Nicodemus

    posted in technical issues read more
  • nico_demus

    So, when opening PD 0.40.3 the PD window is displaying the following errors

    "maxlib: can't load library
    zexy: can't load library"

    on a 2.8 GHz Quad-Core Intel Xeon G5 running 10.5.6...

    Additionally though, I am also noticing that objects like "oneshot" and "onebang" are no longer being recognized as objects within my patches.

    I'm curious about the actual stability of the most recent release of PD in regards to running it on Leopard 10.5.6

    Anyway, does anyone have insight? Further info?

    Nico

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!