Crashes can cause database corruption and database corruption causes crashes so even if we eventially figure out another cause, you should check your file over for possible file corruption and revert to a back up copy if damage is found.
Run a recover on your file and see what it reports. Even if no problems are reported, test the recovered copy to see if it has the same crash issue.
You may also want to try running this database on a different machine, if possible, to see if you get the same crashes.
You may also want to create a small, new from scratch, database file with the same web viewer set up and see if it crashes.
About your web viewer, are you using the web viewer to display data only or is it connecting to a web site? Is it opening any files?
I think it is just being used to display data, but would like to confirm that.
Things to keep in mind about Recover:
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.
I run a recovery with no problems found.
But I could isolate the fault:
When I just open a window with a layout that only contains a WebViewer and then close this window, the system crashes.
Unimportant if the WebViewer is connected to a field or not.
But this only happens in this special file.
In a from scratch test file, everything works fine.
I also changed the table connected to the layout. No success.
The problem also appears in earlier versions of the application. So using a backup file would not help.
But it came up suddenly. Some months ago - in the same files - everything worked.
Neither did I update FM nor Windows. How could this be???
First, take a copy of the file, delete the layout and replace it with a new one. If you have any back up copies that do not show this behavior, you can copy and paste layout objects from it. Otherwise, it is safest to recreate this layout from scratch.
If that works, you've got the issue licked. If not, you may be faced with the option of either rebuilding your file or reverting to an older back up copy.
Note how many times "back up" has come up in this post. Multiple, sequential backups can save you a lot of headaches. I set up a system that automatically makes such a back up copy every 15 minutes when I am developing a new database: Saving Sequential Back Ups During Development
DB's in regular use should have regular backups also built in as part of the system, but usually not on such a tight interval.
I found the reason for the crashes. From my point of view it is a FileMaker Bug:
At least on my computer one must not set the content of a WebViewer to "" and then close the window or leave the layout.
That provokes the crash.
With the content set to "data:text/html,<body></body>" for instance the programm works properly.
this would be well worth reporting in the Report an issue section of this forum. That's where FileMaker techs look for bug reports. YOu can save some typing by copying the link to this thread to your clipboard then pasting that link into your issue report.