Jonny

I was just trawling the forums to see if anyone had registered this bug before (no?) and found that 5.0.2 had been released but i didn't know about it. Shouldn't we (customers) get an email about this kind of thing? Or do i need to specifically subscribe to something?

Anyway, it looks like this hasn't been fixed:

(for me anyway - MBPro 2.33GHz, OS 10.4.11 otherwise all up to date)

While i'm here (sorry) a couple of other points:

Is there a "bug tracker" somewhere we can check and add to?

Sorry to submit a jitter bug here - seemed to make more sense to me.

And finally - ALT + right-clicking on an object in Max4 used to bring up a nice menu with all the current attributes etc on - even in a locked patcher. Clicking on the inlet of an unlocked Max5 object seems to do a similar (but reduced) version of this. How do you do this in a locked Max5 patch?

Sorry for the bundle - it all seems related to me ;)

* Make a new patch
* Add new object: jit.qt.movie
* Click the input and kaboom
(for me anyway - MBPro 2.33GHz, OS 10.4.11 otherwise all up to date)

max5-5-0-2-crashes-on-clicking-jit-qt-movie-inlet-and-a-couple-of-other-things

Im using 5.0.2 and it didnt crash here...

Yep, same problem with 5.0.2 using mbpro 2.16GHz 10.4.11

Also since we're on the subject of Max crashing, I just tried going thru "Improving Your Patching Workflow" here: 

https://cycling74.com/story/2008/5/13/135054/635

"If you aren't sure what object you're looking for, try mousing over the left edge of the new object box and click the "=" button that appears. This will bring up a categorized menu of available objects that you can use to select what you need."

Also since we're on the subject of Max crashing, I just tried going thru "Improving Your Patching Workflow" here: https://cycling74.com/story/2008/5/13/135054/635

when I get to the bit that says:
 "If you aren't sure what object you're looking for, try mousing over the left edge of the new object box and click the "=" button that appears. This will bring up a categorized menu of available objects that you can use to select what you need." 

There is no way to get the quickref menu when the patcher is locked in Max 5. We'll consider it as a feature request for the future, but I wasn't actually aware it could be done on a locked patcher in previous versions, so I would consider it a bug if there were no way to disable it. As for the pop-up menu crashing, this seems to be related to certain relatively rare arrangements of multiple monitors. If you see this crash and can describe your system and monitor configuration to support it might help us track down the problem. I have two monitors configured identically to someone who had the crash and it's never happened for me.

Strange - clicking the = seems fine for me.

Hi David, thanks for the monitors clue - explains why it happens to some and not others.

My setup is a standard 15" MacBookPro with a (cheap) 17" external "SVGA-type" LCD monitor plugged in (1280 x 1024 @75Hz Millions) via the Apple adaptor.

When i click the inlet of the jit.qt.movie object on the external monitor the popup appears fine - but on the built in screen it crashes (log attached). I tried it with a few other objects and it seems if it's a "big" popup it crashes - small ones are fine (e.g. jit.qt.record is ok, jit.qt.broadcast is not - no time to test them all i'm afraid ;)

As far as the quickref menu, i'll double check in 4.6 when i can but i do seem to remember it only worked in Max, not the runtime - it was really handy for checking the values of objects in linked subpatches running in their real environment.

jonny (generally really pleased and impressed with Max 5 - thanks! :)

Sure enough, if I don't plug my second monitor in then the popup works fine.

However, if I DO use my second monitor then the popup still causes a crash if the popup is on the macbook screen, but NOT if it is on the second screen. I have attached the crash report, hopefully this will help you sort this out.

My second monitor is a NEC Multisync LCD175VXM+ connected using the apple dvi->vga adaptor. I have it set up on the left of my mbpro, if that makes any difference...

Sure enough, if I don't plug my second monitor in then the popup works fine. 

However, if I DO use my second monitor then the popup still causes a crash if the popup is on the macbook screen, but NOT if it is on the second screen. I have attached the crash report, hopefully this will help you sort this out. 

My second monitor is a NEC Multisync LCD175VXM+ connected using the  apple dvi->vga adaptor.  I have it set up on the left of my mbpro, if that makes any difference...

Max5 (5.0.2) crashes on clicking jit.qt.movie inlet (and a couple of other things)