6.0.7 render problems
Hi everybody, just installed 6.0.7 and… i’ve been working on some patches which has no problem with max 5 or 6.0.5
patches just crash… A LOT… and i can’t figure out why, just recognized that is a render problem… no render running no problem.
it happend when closing a second patch with a render running or deleting windows or making new gl objects.
it doesn’t crash immediately it start to get slower and slower… it renders for one second and then it stops for one second and then it renders again and then it stops again and so on until it crashes!
MBP 13 inch, osx 10.6.8
Do you have a simplified patch handy? We would be happy to take a closer look if we are able to reproduce.
so i got it finally!
something to do with the gl.slab with slide.jxs loaded!
thats the patch…
follow the instructions!
the patch is super simple so the computer is not really stressed so there is the chance that will survive the crash danger but the render will for sure behave unnormal!
----------begin_max5_patcher---------- 765.3ocyVtsbZCCDF9Z3oP0WkLCwikLFC8pzmilNL9vhQTgjqjb.Zl7tWIYa BowwARYfNvXasVd0u91ckzSCG3kJ1BJOzWQeGMXvSCGLvYxZXPS6AdqS1lwR Ttt4oEEELvaT8q3UqEUZFncuD2Xs1jdWIT6YOJW6g9QyaKSzYKo7h4RHSW2A RPrevHz3w1qjf1q6+DZtarEoqtKzauajIqAMHmC7jTlanBdQVT9dUYs87vg1 KiNxYYlX8ZvH5F+ogs5ZETBbTAy2ZnRBnk.qbAkAOv2jP0HkXMfTPlfmqF8. OiIT.RuD55SPNNf1P44hMna1AJyy5kF1gxEF7fR36zVN8kaGYdNGYGAeeezM 3f6HA1gQcKRB7bPZ9RFCoXhMrcnBvHDcU1OQ2rHQY.DhtvIByjprx0VY5fDT JH+11oHixM5th6lmwcFdao6BAWqn+1QbLwO38iqgSCswR7z.+HSHkD4ZEDcP nMsJsI30l8rPVj5Ft8d9fv+DuCDA2j.3dy2jzDl24J3ygMlg5Mw9UF7+Rbr6 J.R+H5MEFFeNufMeuOQd8WmLywSBwcKlzWgxzK.orHYQopnhddvwQCfISrIT ScqTDF0M.HWuTEMJ07CjIlx+ztQy3SDMoI7BKdZu6b9dC8wL7DGkbqsFG2WJ y3vqd0Uy5YqoRz8to37LASHQXey5A1+X+ySpVKGOBzQBipq55sdaL4pCOEKI sFctMXzkFKzbve0V0I.MrezrH7z3y6ZVXxL2sINHhm0MDw3SDhjyKDa1M1wP KPPglcZMaeYHJSjnsaKiu74ew0mKJr2CFQth4e+xbPLo.giP2mjooOBuGkve FJ8wDZbcFFt25y+gLKm+bGQ5uNqrSQV6ulYJQkLqcNztxJ5EYkCJStjIeRvO rSjW0okz7bfe3AuxoJ6IccyofNidmjdH+momvOPOWX4f+.4XWq5RomiI6I7h ImiJY9Spl5RsjxxGAopwkNgXVHZkPZaNYjqIkW2z4QOI7Hss+wCsd64g+A.r 4J4+ -----------end_max5_patcher-----------
it’s not just a problem that happen with the helpfile of the texture but with any other gl helpfile so i guess with any other patch with a running rendering that is working in parallel.
Good catch. I can reproduce. The patch in my thread doesn’t have slabs though. It does have (capture to) textures.
Thanks for the patch. It appears that this exposes some sort of memory leak possibly in jit.gl.slab. We will be taking a closer look.
All the best,
I have the same thing with capturing to jit.gl.node and next into jit.gl.slab, taking the slabs out fixes everything
Any more insight on this problem, I’ve had to restart my computer a couple of times today when using jit.gl.slab with gaussian blurs, and brcosa! There is defenitly something leaking there.
I have to restart Max all the time because of this. Very annoying. Hope it gets fixed soon!
ya! i had to go back to 6.0.5 ’cause i’ve to many patch that risk to crash in the middle of a show
where to download 6.0.5?
just chiming in to say that this memory problem has been driving me crazy this weekend – I’ve got a few slabs cooking but if I start editing the patch (in any state of activity), virtual memory gets eaten up like candy and Max starts falling over itself and will crash if I don’t get rendering stopped (which is hard to do when the UI isn’t responding).
We are working on a fix for GL rendering and should have something available soon.
If you do need to use Max 6.0.5 in the meantime, you can download it here:
As far as I can tell at the moment, this is an unrelated issue and something that needs a better example, as we are unable to reproduce the results here.
anyway to install 6.0.5 alongside 6.0.7?
Just rename your Max folder to Max607 or something you like and install 6.0.5. it will install as Max which you can also rename to Max605 or so.
wondering if the "Jitter OpenGL: various fixes for rendering slowdowns and crashes" of 6.0.8 means this is all in the past?
Indeed, it is the hope that these issues are now fixed. Let us know if you see any further problems.