Created attachment 60380 [details]
So, with the attached .pptx around slide 20 we end up doing...
XCreatePixmap (dpy=0x202e400, d=<optimized out>,width=187690, height=187580,
which will fail cause that's just way too large
I'm stumped by this one, but I attach a debugging patch and some debugging output and I think the massive numbers come from Shape::createAndInsert
Created attachment 60381 [details]
Created attachment 60382 [details]
debugging log, grep for "this is getting suspicious" and "HUGE"
caolan->rodo: I'm guessing you know how the transformation stuff is supposed to work to be able to see if its working like it supposed to
Caolan McNamara committed a patch related to this issue.
It has been pushed to "master":
Related: fdo#48961 don't crash on silly pixmap sizes
Comment on attachment 60381 [details]
this patch is just for debugging so i'll remove the "patch" flag; also it looks like something has been committed, is this bug FIXED?
No, not fixed. I just clipped stupid pixmap sizes to max legal sizes (like happens in the vcl-only code already). The debugging patch shows where they come from but I don't quite understand the logic of the transformations there to know which (if any) are wrong.
If I open the file with LO 22.214.171.124 (Win7 Home, 64bit) and compare it with MSO 2007 then I can recognize several bugs: slide 2 (text effects), slide 3 (rectangle effects), slide 14 (picture inverted), slide 20/35 (text inverted and displaced), slide 24/27/28/30/31 (charts totally messed up), slide 25 (color of the lines), slide 40 (text effects)
I don't get my warning anymore, so seems fixed