Summary: | dxcanvas BitmapCanvasHelper GDI+ Crash on Windows | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Yousuf Philips (jay) (retired) <philipz85> |
Component: | Impress | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | critical | CC: | ilmari.lauhakangas, sebastiaan.veld, serval2412, thb |
Priority: | high | Keywords: | perf |
Version: | 4.5.0.0.alpha0+ Master | ||
Hardware: | Other | ||
OS: | Windows (All) | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Attachments: |
crash screenshot
Screenshot crash error |
Description
Yousuf Philips (jay) (retired)
2015-03-25 07:48:32 UTC
@Thorsten: Meeks suggested i CC you on this. ;D Tried it on Win (zoom to max), didn't crash, but got the worst freeze ever.. Whole OS turned into molasses. I was able to close LibO gracefully, but it took like 20 minutes. Setting to NEW, as my experience was close enough to a crash.. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ (x64) Build ID: a51ac4d2bb8c4f1ea1d4ea7569863e2fb6535b02 TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-06-22_21:37:53 Locale: fi-FI (fi_FI) Created attachment 119034 [details] Screenshot crash error I have the same crash error opening an .xlsx document using LibreOffice 5.0.1 and 5.0.2 on Windows 7. On my OSX machine with LO 5.0.2 the same document just will not open and does not show a visible error. I can provide the document to someone that want to work on this problem, plz send me an email at sebastiaan.veld@gmail.com. @Yousuf: How did you add the video (step-by-step)? (In reply to Armin Le Grand from comment #4) > @Yousuf: How did you add the video (step-by-step)? Armin: I didnt produce the video, i was watching the video and noticed the crash. Migrating Whiteboard tags to Keywords: (perf) Yousuf: do you reproduce this on recent LO version (5.1.3)? Here's the location where it failed according to the message: http://opengrok.libreoffice.org/xref/core/canvas/source/directx/dx_bitmapcanvashelper.cxx#92 91 ENSURE_OR_THROW( 92 Gdiplus::Ok == pGraphics->SetCompositingMode( 93 Gdiplus::CompositingModeSourceCopy ), // force set, don't blend 94 "BitmapCanvasHelper::clear(): GDI+ SetCompositingMode call failed" ); Considering these links: - https://msdn.microsoft.com/en-us/library/windows/desktop/ms535808%28v=vs.85%29.aspx - https://msdn.microsoft.com/en-us/library/windows/desktop/ms534175%28v=vs.85%29.aspx I wonder if it could be interesting to retrieve the value returned by SetCompositingMode call. (In reply to Julien Nabet from comment #7) > Yousuf: do you reproduce this on recent LO version (5.1.3)? I've never produced the issue myself, i've seen it produced while watching the tutorial video mentioned in the description. Still getting a bit hangy behavior, but nothing as severe as my comment 2. Win 7 Pro 64-bit Version: 5.3.0.0.alpha0+ (x64) Build ID: f536a83d51443d19dba58157cea28fb67a090e02 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2016-06-13_01:19:21 Locale: fi-FI (fi_FI) *** This bug has been marked as a duplicate of bug 108552 *** |