Thank you for your post.
This is expected behavior. Interactive container fields are identical to Web Viewers. The data is accessed using the OS Webkit, and much of that data is cached for later viewing so that the PDF is not loaded each time the record is accessed. Once the file is closed, the memory is released.
That is really not an acceptable answer. It should be controllable. FileMaker shouldn't make the assumption that we want things cached. What I am discovering is that FileMaker likes to make a lot of assumptions about what the customers would want rather than give them options.
So after some serious testing on this today I have a workaround. It is far from ideal but I wanted it to be posted so if anyone else comes across this at least they have an idea
Its pretty simple, but it doesn't actually close out the webkit.All it does is to keep the memory from spiraling out of control.
- Freeze Window
- Go to a different layout on the same table
- Go to the next record
- Return to the original layout
This has kept my webkit from exceeding 20mb used.