Debugging through a script with Data Viewer evaluating a pretty simple ExecuteSQL statement crashes FMPA17v3.
It crashes without the crash log option to send to Apple.
Please check ~/Library/Logs/DiagnosticReports folder for crash report and post a download link to get it.
Any plugins installed?
I also experience several crashes during the day. I checked with plugins (MBS and Baseelements) and without plugs installed. This doesn't make a difference. Going to the data viewer crashes FM 1 out of five times. This is a serious bug.
( macOS 10.14.2, Filemaker 17.03, MacBook Pro 2017, i7, 16g memory)
No plugins on my Mac. Thanks for confirming!
FileKraft and joshofman:
Thank you for your posts.
If FileMaker Pro is crashing, a crash report should be available. The location from monkeybreadsoftware is correct (Thank you!).
Please post the crash report up to and including the crashed thread. Or, attach the crash report to a reply. The crash report will let me know what area of FileMaker is causing the crash.
Please find attached some crash reports…
Most of these crash reports are identical and involve a calculation.
Do any of your calculations in the Data Viewer - Watch tab - return an invalid or infinite result (e.g., dividing by zero)? Possibly displaying a "?"
Do you have a macOS High Sierra machine? If so, are you able to reproduce the crash? I'm trying to determine if Mojave is a contributing factor.
No, of course not
Normally it is a calculation with a normal result, but the crash occurs normally upon re-entering the data viewer. It can be that the context has changed (another layout, I am working with a interface file only. It is rather a heavy interface file with lots of tables connected, but that never was a problem.
I also remarked that every calculation editor (also when editing scripts) takes more time to become active. Previous to FM17 it was almost instantly, from FM17 onwards it takes almost 5 seconds!
Thank you for the additional information.
Do you have access to a macOS High Sierra machine? I asked previously because our Development and Testing departments are aware of an issue with Mojave and evaluating an invalid expression. Another two Community members have run into that particular issue:
FileMaker Advanced quits unexpectedly during ordinary use of Data Viewer
In regards to entering the Calculation editor, I am unable to reproduce the issue, as it opens within one second. Can you provide more information about your computing environment? Any plug-ins installed/enabled? If so, remove/disable the plug-in(s) and see if the issue still occurs.
The crashes and sluggishness occur also without any plugins installed
FileMaker 17.01…17.04, macOS 10.14.2, MacBook Pro i7 (2017), 16g memory., but also occurs on an iMac.
I always develop when my file is open on FIleMaker Server (latest version)
All the development is done in an inteface file in a development copy of the complete production environment. In the development enviroment normally only 3 machines are logged in.
Are you able to reproduce the "sluggishness" locally?
Testing confirms the crash reports are nearly identical to a crashing issue with the Data Viewer returning an invalid result. Your post has been attached to the original report. When more information becomes available, I will let you know.
Besides the remaining Log files, Testing has asked for a copy of your solution. I have sent you a private message with instructions where to send the solution.
attached crash report - happened again but data viewer was just displaying left panel - no complex equation there ..
Your crash report is slightly different. Do any of the watched variables return an invalid result?
thanks TSGal for responding!
Before it crashed it displayed an error evoked by a proceeding find on a layout where the find aimed at unrelated fields - the find did not result in an error but displayed a prompt stating "This operation cannot be performed because one or more of the relationships between these tables are invalid".
This actually would be another bug to report because the find just escapes into browse mode without an error to capture..
Thank you for the information.
Find on an unrelated field should produce error 103 (Relationship is missing), and it is expected to return to Browse mode after an invalid Find.
Is the relationship supposed to be valid?
The relationship has been fixed - that was my mistake - but I can still replicate the failing without error 103 with the unrelated TO finds - the crashing cannot be replicated reliably though ..
If you can replicate the unrelated finds without an error, please attach a sample file.
yes I can replicate it reliably but the file is local and part of a complex solution (incl. 2 files on server) so to provide the file
it requires preparation and the efforts might not be worth it because almost all bugs reported won't get fixed anyway.
Retrieving data ...