Filemaker 10 Runtime with Scriptmaster Crashing

[mtwalker]

I have solution that uses Scriptmaster. I have had a few Mac users reporting crashes when opening the solution. I have not been able to resolve the problem for them. I have received crash reports from 2 of the users and they both mention "JNI_CreateJavaVM" . It appears that it may have something to do with Java. Any suggestions?

Thanks.

Crash Report:

Runtime

Identifier: com.filemaker.client.runtime

Version: 10.0.3 (10.0.3)

Code Type: X86 (Native)

Parent Process: launchd [89]

Interval Since Last Report: 9118 sec

Crashes Since Last Report: 1

Per-App Interval Since Last Report: 6 sec

Per-App Crashes Since Last Report: 1

Date/Time: 2009-12-14 16:44:50.281 -0500

OS Version: Mac OS X 10.5.8 (9L31a)

Report Version: 6

Anonymous UUID: 2BF33FA5-A1FE-48C6-8D52-67D3742EEB05

Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

Crashed Thread: 0

Thread 0 Crashed:

0 libhotspot.dylib 0x96e40b7d JNI_CreateJavaVM_Impl + 1005

1 libhotspot.dylib 0x96e4fa01 JNI_CreateJavaVM_Impl + 62065

2 com.prosc.jack3 0x0237ae0d getPluginBridge(JNIEnv_*) + 253

3 com.prosc.jack3 0x02370ef8 doInit(short, short, unsigned short*, long, bool, long, long) + 264

4 com.prosc.jack3 0x023709eb FMExternCallProc + 251

5 ...ilemaker.dbengine.framework 0x0173b115 Draco::DBPlugIn::SetEnabled(bool) + 389

6 com.filemaker.client.runtime 0x000e29a2 LoadFMPlugIns(Draco::Directory const&, std::vector > const&) + 210

7 com.filemaker.client.runtime 0x000e2f9f CFMProApp::InitInstance() + 1071

8 com.filemaker.client.runtime 0x00372e44 CMacApp::Main() + 52

9 com.filemaker.client.runtime 0x000dfe75 main + 37

10 com.filemaker.client.runtime 0x00003102 _start + 216

11 com.filemaker.client.runtime 0x00003029 start + 41

[shmert]

Which modules are you using? Anything with timers or callback scripts?

Edited December 15, 2009 by Guest

[mtwalker]

I'm using:

Call Script Immediately

Post Data To URL

Run Shell Script

They are initialized in my startup script. "Run Shell Script" is called after the startup script to check the status of the user's license. The other 2 modules are not called until after the solution is up and running, depending on what the user is doing.