https://bugs.documentfoundation.org/show_bug.cgi?id=160644
--- Comment #12 from Patrick Luby (volunteer) <guibomac...@gmail.com> --- (In reply to Sam from comment #10) > I've checked font validation again (via Font Book), and I'm told that still > all "font files passed. These files should be safe to use" (that is, none > have warnings). Unfortunately, your latest sytem crash log is still showing "fontd" as the cause of the crash. So it appears that the system crashes aren't due to a particular font and is probably due to some other cause. I took another look at your LibreOffice crash log in attachment #193711 and noticed that LibreOffice was using nearly 4 GB of memory when it crashed. So maybe LibreOffice is slowly grabbing more and more of system memory (i.e. a memory leak) and then, when LibreOffice requests some font data, there is not enough unused memory available for fontd to handle the request. In comment #6 you mentioned that one of the system crashes occurred when you tried to print a document. Printing embeds partial copies of the fonts in your document into the printed output. Also, printing temporarily increases LibreOffice memory usage and that usage may be quite large if your document contains images. Can you launch the /Applications/Utilities/Activity Monitor application and click on the Memory tab? Then, launch LibreOffice and open the document that you were using at the time of the last system crash. In Activity Monitor, find and select LibreOffice. Then, print to Preview in LibreOffice a few times and watch the Memory column for in Activity Monitor. Does LibreOffice's memory usage keep increasing every time you print? If yes, does memory usage drop significantly after you close all documents (but not quit) in LibreOffice? -- You are receiving this mail because: You are the assignee for the bug.
