https://bugs.documentfoundation.org/show_bug.cgi?id=70154
Michael Meeks <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #31 from Michael Meeks <[email protected]> ---
Hi Aron; thanks for reproducing, and doing it with a symbols build.
Unfortunately the trace is not so useful:
FAILURE_BUCKET_ID:
MEMORY_CORRUPTION_LARGE_SHUTDOWN_c0000005_memory_corruption!ntdll
It means that somewhere before this trace someone did something bad to the
memory. However - if you have that VM setup, what would be really useful is
running 'drmemory' on the binary:
That should make the app run -much- slower (20x at least), but it should also
produce a big log that shows where this memory corruption occurs [ with stack
traces ].
Do you think you could run it under drmemory ?
Thanks !
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
