Forums > MaxMSP

07mNumericalUserInterfaces.maxpat crash

October 10, 2008 | 8:53 pm

Hello,

Another problem with a tutorial patch: 07mNumericalUserInterfaces.maxpat.

When I change the number box connected to ‘size $1′ Max crashes.

Max 5.0.5
10.5.5
MacBook 2.4G Intel

Thread 0 Crashed:
0 com.cycling74.MaxMSP 0x0034ca4f juce::Path::lineTo(float, float) + 255
1 com.cycling74.MaxMSP 0×00130803 jgraphics_line_to + 89
2 com.cycling74.MaxAPI 0x02a88a2e jgraphics_line_to + 75
3 com.cycling74.dial 0x18ab5d11 jdial_paint + 634
4 com.cycling74.MaxMSP 0x000fbe1a BoxComponent::paint(juce::Graphics&, juce::AffineTransform const&) + 1148
5 com.cycling74.MaxMSP 0x001ba447 ZoomableComponent::paint(juce::Graphics&) + 43
6 com.cycling74.MaxMSP 0x002de3d9 juce::Component::paintEntireComponent(juce::Graphics&) + 1081
7 com.cycling74.MaxMSP 0x002de456 juce::Component::paintEntireComponent(juce::Graphics&) + 1206
8 com.cycling74.MaxMSP 0x001a0a12 PatcherLayerComponent::paintEntireComponent(juce::Graphics&) + 80
9 com.cycling74.MaxMSP 0x002de456 juce::Component::paintEntireComponent(juce::Graphics&) + 1206
10 com.cycling74.MaxMSP 0x002de456 juce::Component::paintEntireComponent(juce::Graphics&) + 1206
11 com.cycling74.MaxMSP 0x002de456 juce::Component::paintEntireComponent(juce::Graphics&) + 1206
12 com.cycling74.MaxMSP 0x002de456 juce::Component::paintEntireComponent(juce::Graphics&) + 1206
13 com.cycling74.MaxMSP 0x002de456 juce::Component::paintEntireComponent(juce::Graphics&) + 1206
14 com.cycling74.MaxMSP 0x002de456 juce::Component::paintEntireComponent(juce::Graphics&) + 1206
15 com.cycling74.MaxMSP 0x002de456 juce::Component::paintEntireComponent(juce::Graphics&) + 1206
16 com.cycling74.MaxMSP 0x00422ec0 juce::ComponentPeer::handlePaint(juce::LowLevelGraphicsContext&) + 48
17 com.cycling74.MaxMSP 0x002a1d06 juce::HIViewComponentPeer::RepaintManager::paint(CGContext*, int, int, int, int) + 806
18 com.cycling74.MaxMSP 0x002a354d juce::HIViewComponentPeer::hiViewEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 2509


October 10, 2008 | 9:09 pm

… obviously form the crash report it’s dial that crashes and it’s when the ‘size’ message has an argument less than 2.


October 10, 2008 | 11:50 pm

On 10 oct. 08, at 14:09, Martin Robinson wrote:

> … obviously form the crash report it’s dial that crashes and it’s
> when the ‘size’ message has an argument less than 2.

This is a known issue already fixed for the next incremental release.
Thanks.

ej


Viewing 3 posts - 1 through 3 (of 3 total)