crash

problems with quartz composer patches... crash with dad files, convolution filters don't work...

pagina223's picture

hi, wanted to see if anyone can enlighten me with my problems about quartz composer: 1. when I load Collada files (.dae) the program shuts down, do not load. other 3d files (.obj, ...) if the load but not rendered ... 2. image filters "convolution" (3 by 3 convolution, ...) do not work, even adding a patch "image crop". I work with mac mini Intel Core i7 4GB 1600MHz DDR3 graphics card Intel HD Graphics 4000 1024MB -The Quartz composer version is 4.6.1 and the operating system is Yosemite. to see if someone can help me. thank you very much !!!

Reading a Crash Report

scalf's picture

I am wondering if we can gather some ideas in one place for reading crash reports, spin dumps, and other messages. Then how to interpret and make use of them within Quartz Composer

Sometimes it is obvious why a program crashed, other times you look at the crash report and it is not always obvious what it says - to the untrained eye.

-> Which are the right reports to look at, and where can they be found, after Quartz Composer crashes/freezes/stops responding?

-> What parts of the report are important to look at?

-> How can one make use of them?

sinsynplus started a thread over here but I think there can be more http://kineme.net/forum/General/readingacrashreport

Thanks for any tips or resources!

Crashes when using Capture patch / QCAsynchronousQCView

pyramus's picture

Hi everyone,

I'm posting this to possibly save others the headaches and frustration I was encountering until a minute ago.

PROBLEM: Whenever I had a Capture patch embedded in a composition (about 90% of the time in my case), I couldn't safely restart the viewer -- 95% of the times QC would just stop responding or even crash. Luckily KinemeCore tried to auto-save the composition (thanks for that!) so I didn't really lose much work. However, I did feel losing a lot of time, self-confidence and maybe even karma with all those crashes.

SOLUTION: So, after a looooot of trial and error I found out it was the QCAsynchronousQCView that I (accidentally?) checked in the extended preferences that was bothering my system. After unchecking this and a restart of QC I didn't have any trouble.

N.B. Probably someone else here can better explain the actual reason for this trouble. I know these options are all unsupported, for advanced users and "at own risk" and all, but at least I'm hoping someone else with similar trouble will now find this post. I know I would have liked that :)

pyramus

Quartz crash corrupts related compositions

scalf's picture

I have this problem with a file, more than once.

I am making a Vj mixing program by the name of Senses. It loads files from a directory, applies effects, then outputs etc.

I have this problem. I get it working and then I save, quit, come back to it in a few minutes and Quartz crashes loading it. It will open a blank composition, create and save a new one no problem. But, if I load the last save of Senses, or any previous rendition (v 1.0, 2.0, 2.2, etc) it will crash. Interestingly enough, I loaded this on a 2nd machine which is also running 32-bit QC 4.0 with 10.6.8 and a mirror of the plugins it loaded but with the below error report. It changed some of the routing of patches to get it to run when I hit okay after seeing the report.

I read the crash report and I get the report below.

I tried clearing the p.list, but that changed nothing. I tried uninstalling through the terminal, then reinstalling Quartz and no changes in condition. Removing certain plugins. The first time this occurred I tried scrubbing and reinstalling everything and that was the only time I was able to reload the last saved version with no grief (composition saved onto zip drive). But now, after three days since reinstalling and much work done I have encountered this problem again. I am sure one can imagine that this is unfortunate, and adds some insecurity to using Quartz Composer not knowing the cause just yet. But I know this is fixable and must be preventable.

I have come up with a few ideas

  • There is some runtime or path configuration that is causing the knot. Why it came up now I don't know. Perhaps if we could isolate and delete it would fix the flow.
  • I have loaded the comp on a 2nd computer, deleting selected portions and running it on the 1st machine. Some load and some don't. Through isolating the bad patches I have found that certain sections of code are faulty. When the "RGB_On" or "Vj Module" were deleted the comps would run once again. However it is a vast chunk of the patch work and not just a line or two; seemingly.
  • Is there a way to investigate further through a different log or crash report
  • Could it have gotten hung up reading a file and gotten "stuck"?

Has anyone experienced anything like this? What I don't understand is how previous versions of the file would not work after a crash that happened many saves and version later? It even happens to versions of Senses loaded from quarantined computers as well.

I aim for this project to be running smooth and open one day. I would really appreciate if anyone might be able to load this up and see if there were any apparent problems in the coding that kept it from running.

Any feedback would be much appreciated,

 Casey

Channel 1 Cannot create connection from ["Image_Out" @ "Patch_6"] to ["Channel_1_Global" @ "Patch_2"]

Channel 1 Cannot create connection from ["RGB_On" @ "Patch_6"] to ["For_RGB_Glitch" @ "Patch_13"]

Channel 1 Cannot create connection from ["RGB_Count" @ "Patch_6"] to ["RGB_Count" @ "Patch_13"]

Channel 1 Cannot create connection from ["Image_Out" @ "Patch_6"] to ["inputImage" @ "Sprite_1"]

Channel 1 Cannot create connection from ["RGB_Time_Memory_Dump" @ "Patch_6"] to ["inputRZ" @ "Sprite_3"]

Channel 1 State restoration failed on node "RenderInImage_1"

Vj Module State restoration failed on node "Patch_1"

Senses Render State restoration failed on node "Patch_1"

Senses State restoration failed on node "RenderInImage_1"

Macro Patch State restoration failed on node "Patch_1"

(null) State restoration failed on

Quartz builder crash

-polygon's picture

Hi, everyone, :D

Anyway, I updated yesterday to 10.6.6. and QuartzBuilder started crashing. :l Don't know if it's the update, cause I haven't used it for two weeks or so, but today I needed it for a very important school project lol, and it opens normally, but when I load any .qtz file it just crashes.

I attached the error report.

I noticed now that when I quicklook a .qtz it crashes Finder :l, but when I just open it in QC then everything works fine.

Help?