On Fri, Jan 12, 2018 at 01:31:14PM +0100, Daniel Pocock wrote: > If it is able to save correctly and show that window, it would be useful > if it gave some clue about why the crash happened, e.g. did a malloc > call fail, is there a stack trace? The window doesn't give the user any > hints to troubleshoot further.
gdb? strace? > I'm guessing it may be an issue with low physical RAM on a host that > doesn't have dedicated video RAM but the errors don't give me enough > detail to be certain. Which still would be a LO bug why? You didn't answer any of the points I raised in my reply. Regards, Rene
