Can't tell from here.
If you create a brand new file and copy/delete fields solely from within this one file, do you get a crash?
If you recover the file that is crashing and try again on the recovered copy, do you get a crash?
I didnt try that, but if I will make a new layout and copy a field my filemaker will crash, and If I will try to delete that field my filemaker is crashing too.
Please try that on a completely new file.
I did recover the file and same thing happen.
What operating system are you using? Are you running any plugins?
To repeat, please try this action on a completely new file.
Recover often fails to detect the fact that a layout is corrupt. So testing this on a completely new file may tell us something useful.
good question; it has been happening on my system since clean installing fm15 on OSX.11 on a MBP.
FM14 had similar problems.
It does seem to be a consequence of copying elements between files. Which I try and totally avoid as mush as possible; when I do resort to doing it, close quite and reboot FM is some insurance, but very tedious workflow.
On OSX, monitoring Activity Monitor often shows substantial memory use by FM for very simple procedures.. This will cause real slow downs , such that the 'pizza wheel' can be displayed even as a result of copying some simple text from one field to another.
A simple copy a line of text can show memory use 35-c.50%CPU, and the process run for 10-15 secs or more.
At times other relatively simple process trigger CPU use to near 100%, for extended times - I have taken to opening Activity Monitor frequently.
I would estimate 40 + crashes in the last 3-4 months.
As a wild and unsubstantiated guess - a memory leak something to do with FM clipboard processes and cache resolution looks like a candidate.
And yes it happens to a number of different files, and even new test files.
I script clone file sets at most minor build build changes ( change a script line, add a button, field...) so I have fallback to re-instating uncorrupted files, but it is a (< insert expletive of choice>) pain in the (< insert anatomical region of choice>).
Spawning a pizza wheel anytime has become a flag to open Activity Monitor, and if I don't want to live dangerously, quit and do a restart; which may or may not re-establish a clean slate.
1 of 1 people found this helpful
There are reports over in Report an Issue that copy/pasting a popover with a merge field in it can cause crashes and destroy a layout. If you've worked with a popover on the layout, that may be the issue.
doesn't sound like my initiating events
I don't copy layouts
I rarely use merge fields
Copy a popover at times, but more often is might be script lines
I dont use any plug ins...Im using windows 7.
I think you are right..because I have a pop over with a merge field. Im trying to delete it but I cant delete.
That fits the bug reports that I just read earlier today.
Sent from my iPhone