Plugin Scan Crash / Absynth 4 demo crashes JUCE


#1

Got some user having a problem when scanning VST plugins on OS X with my JUCE app, even if he only scans 1 single plugin the error report on the bottom comes up. Actually it seems not to scan before crashing.

Now, I searched for this “Non-contiguous memory does not support view” error message but could not find any info on that - I don’t know what it means, do you maybe know?

My application is linked with debug information, it just seems not to have any effect for the stack trace on this system with OS X 10.5.6 . I’m using JUCE 1.46 in my app (with AU/VST hosting bug fixes), it does nearly never crash on my system during the scan, so I don’t know why it does on this system.

Any help appreciated :roll: Thanks!

PS: NI Absynth 4 FX crashes the JUCE PluginHost in function VSTPluginInstance::getVersion() . I am investigating…

Version: ??? (1.0)
Code Type: X86 (Native)
Parent Process: launchd [84]

Date/Time: 2009-05-20 21:32:11.577 +0200
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c0000000
Crashed Thread: Unknown

Error Formulating Crash Report:
Non-contiguous memory does not support view
0x9357b10b
0x9009ae3b
0x0007aa18
0x00075438
0x0007498c
0x000748f7
0x0008985c
0x00089570
0x00085049
0x00002e74
0x000094a2
0x0000b5d4
0x0000b121
0x94d5803b
0x0000a828
0x94d2c095
0x94d2bf52

Backtrace not available

Unknown thread crashed with X86 Thread State (32-bit):
eax: 0x000000ff ebx: 0x0011c5c9 ecx: 0x00034814 edx: 0x00187034
edi: 0x000006bc esi: 0xffffffff ebp: 0xbfffe538 esp: 0xbfffe4f0
ss: 0x0000001f efl: 0x00010206 eip: 0x0009716e cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0xc0000000

Binary images description not available


#2

Solution here: http://www.rawmaterialsoftware.com/juceforum/viewtopic.php?t=2427