I've posted here because I'm wondering if I have some circular relationships or definitions that are causing the crash (and how can I find out?) I was amazed to find virtually nothing, anywhere, on EXC_BAD_ACCESS (SIGBUS).

I have a db which causes FM to crash consistently on first action after launch, regardless: menu click, button select, etc. FM works fine with other db's.

This occurred occasionally before and seemingly randomly. There was a time when duplicating the doc and relaunching bought me some use; that was never a solution but was a workaround. No longer.

Now it's a unavoidable. The db is quite small, 8 tables, <25 fields each, <75 records each, 5 layouts, no media, containers, graphics, or anything (overtly) messy. It's 384k.

I've restarted, repaired permissions (nothing amiss), tossed the FM pref's; no change. Note, it's current (10.0.3), I'm not running Snow Leopard, and the pref trash was not beneficial (even once).

I'm very open to suggestion. Many thanks in advance. /J.

Details:

Model: MacBook2,1, BootROM MB21.00A5.B07, 2 processors, Intel Core 2 Duo, 2.16 GHz, 2 GB

Version: 10.0.3 (10.0.3)

Code Type: X86 (Native)

Parent Process: launchd [94]

OS Version: Mac OS X 10.5.8 (9L31a)

Anonymous UUID: 62B10A07-E398-4663-8C39-65B71965C1DB

Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000404

Crashed Thread: 0

You seem to assume that there is a problem with the FileMaker Pro program. Have you gone through the usual routine of repairing the database file itself?

1) backup

2) save a compressed copy and see if it's better; else

3) use the recover command

The recover command recovers data at the expense of structure, so it's best to import the data from the recovered file into a known-good backup of the database.

Thanks, Vaughan, many helpful thoughts.

But au contraire, since all of my other db's function perfectly, the problem is definitely just this one file (and copies thereof).

I had not pursued your suggestions (and was ignorant of Recover ...). I now have.

The Compressed Copy worked for about 30 sec, then quit. Subsequent openings now quit on launch.

Similar behavior out of Clones, Duplicates, etc. (Obviously, all of these required multiple attempts to get FM to stay open long enough to access the File Menu ; )

Recovery Consistency Check found no problems on either the original (or any dupes or Clones). After Recovering, there were no problems reported, but the same behavior is exhibited out of the Recovered File: FM Quits on launch or very soon thereafter.

I'm really at a loss and would welcome further insight. As it's so small (down to 132k) I'm attaching in hopes that someone's peak under the hood will cause a realization. Many thanks in advance, /J.

I'm attaching in hopes that someone's peak under the hood will cause a realization

I would - but no attachment.

Okay, I _would_ attach, but - while fearing I'm showing my ignorance - I haven't figured out how to do that. I have no 'attach' option, and FMForum Help simply says "If File Attachment is enabled ...". Help here, as well, gladly accepted.

See if this helps

Link

Lee

Ah (thank you Lee), as promised, the db.

adb.fp7.zip

It runs fine on FM9, OS X 10.4.11

Runs fine for me. I see the design included repeating fields, which generally should be avoided, in favor of a real related table. But that is a design issue and not related to crashing.

Given that your on a Mac then I find it hard to conceive the idea of a VIRUS!

A wonky plugin, maybe?