We’ve created a script to help with navigation that mitigates the problem by forcing FileMaker to release the memory through viewing a layout that doesn’t have any fields or web viewers on it. If you navigate to five or more records that contain a web viewer on their layouts, FileMaker reserves and holds the system’s memory.

This upgrade seems to be accompanied by a memory leak problem. We have our long-awaited upgrade to using WebViewer2 for Microsoft Edge! Not only does this upgrade minimize security vulnerabilities and incompatibilities, but it helps solve the old bug of PDFs not always displaying correctly on Windows computers. Is this a significant enough bug to prevent you from installing the upgrade? No.

Launch FileMaker (if it’s already running, we advise quitting and relaunching.) After opening FileMaker, you can deactivate the Rosetta option and it will continue to function as intended. In the Info window, check the box labeled “Open using Rosetta.” Close the Info window. Select FileMaker Pro Advanced 19 and press Command + I. Restarting the computer did not resolve the problem, nor did quitting and relaunching FileMaker.ĭespite Claris stating that FileMaker is now a Universal macOS app, you still need to install Rosetta to have it fully functional and stop this error-though it doesn’t have to be activated. When we downloaded and installed FileMaker Pro Advance 19.3.1 on a brand new MacBook Air using the M1 processor that we hadn’t used in any manner previously, we installed FileMaker Advanced Pro 19.3.1 Every time we tried to launch it, we encountered an Unknown Error-1 message.

Filemaker pro 17 big sur