https://bugs.documentfoundation.org/show_bug.cgi?id=106526
--- Comment #1 from cr...@arno.com <cr...@arno.com> ---
Looking at the crash report, it appears calling routines and line numbers are
reported (i.e. great diagnostic information).
A cursory code look, I would suspect trouble starts at
https://cgit.freedesktop.org/libreoffice/core/tree/slideshow/source/engine/slideshowimpl.cxx?h=libreoffice-5-3#n1382
in the addView() routine when the second call to add the Presenter's screen is
called.
I see a number of design patterns used which aren't in my background, so a
developer more practiced in these patterns and this specific code area will
need to do the debugging.
I hope it will be relatively straightforward for a developer to discover why
this code fails on a dual 4K screen and works fine on a dual 1080p screen set.
My guess is there is a constant or two for memory allocation which needs to be
updated from 1920x1080 to 4096x2160 so memory isn't overflowed and corrupted by
a pointer passing a boundary and writing where it shouldn't. This is based on
watching the screen initially paint right, then be overwritten and corrupted by
what I assume is an update pass.
This code will not work on today's current batch of 4K laptop screens with
auxiliary 4K monitor, like what I'm running.
Let me know if I can help whoever is looking at this issue.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
