Bug 108384 - Crash with "Could Not Create System Bitmap" error
Summary: Crash with "Could Not Create System Bitmap" error
Status: RESOLVED DUPLICATE of bug 108368
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.3.3.2 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-07 03:55 UTC by Kevin
Modified: 2017-07-26 09:13 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
cells I was working with at the time of the crash and system bitmap error (11.58 KB, application/vnd.oasis.opendocument.spreadsheet)
2017-06-07 04:00 UTC, Kevin
Details
dump file from users/appdata (146.61 KB, application/octet-stream)
2017-06-07 04:02 UTC, Kevin
Details
dump.ini from users/appdata (192 bytes, text/plain)
2017-06-07 04:02 UTC, Kevin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin 2017-06-07 03:55:12 UTC
Description:
"Could Not Create System Bitmap" error is displayed - okaying causes crash with no message or signature.

Steps to Reproduce:
1. open my usual large Beatles spreadsheet (attached to several reports)
2. select a region of characters and apply Bold command


Actual Results:  
"Could Not Create System Bitmap" error - crash

Expected Results:
no crash?


Reproducible: Always

User Profile Reset: No

Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
Comment 1 Kevin 2017-06-07 04:00:32 UTC
Created attachment 133884 [details]
cells I was working with at the time of the crash and system bitmap error

Here are the cells I was working with at the time of the crash (pasted into a fresh document).

NOTE: I messed up when creating the report and left reproducible at its default setting of "always" - this bug is NOT reproducible in any consistent way. It's kind of a bug that Bugzilla doesn't let you edit your comments and reports, but that's not your problem.
Comment 2 Kevin 2017-06-07 04:02:26 UTC
Created attachment 133885 [details]
dump file from users/appdata
Comment 3 Kevin 2017-06-07 04:02:47 UTC
Created attachment 133886 [details]
dump.ini from users/appdata
Comment 4 Telesto 2017-06-07 10:31:31 UTC
Testfile: attachment 133856 [details]
Comment 5 Buovjaga 2017-06-11 10:24:21 UTC
I wonder why the crash dump was not uploaded to the crash server.. this does not exist: http://crashreport.libreoffice.org/stats/crash_details/8e4d50ce-e55f-426c-bbb5-079885346975
Comment 6 Markus Mohrhard 2017-06-11 21:36:06 UTC
There are two different IDs involved. The local name of the file which needs to be locally unique and the server ID. They don't match at all as the file name is not important on the server and we need to have a globally unique ID across all uploaded reports. You need to search for the ID that was shown to the user when he uploaded the report.
Comment 7 Timur 2017-07-26 09:13:33 UTC
This bug may stay open but I'm afraid it's of no use since there's no Crash Report and it's not reproducible, so it can't be confirmed like this. 
I'll mark as a duplicate of Bug 108368 for now. If it reproduced with more info, please set back to Unconfirmed.

Kevin, please consider a large number of bugs and help even more when there's a case like this, intermittent bug: 
* what: use procdump (part of free and useful Sysinternaly Suite) during LO run in order to get a dump (soffice.bin.dmp)
* how: run procdump manually after LO start (path-to\SYSINTERNALSSUITE\procdump.exe soffice.bin -h path-to\soffice.bin.dmp) for reproducible bugs like this one, OR via simple batch file like attachment 129814 [details], that is used instead of LO icon to start LO, for intermittent bugs (which seems to be the case here)

and upload previous crash dump with LO "Master x86 39" or even do it yourself:
- analyze dump with WinDbg configured per https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg (set "Symbol File Path")
- attach here as an attachment result of "!analyze -v" command in WinDbg (that's "backtrace") 
- if "!analyze -v" is empty, which comes after "ntdll!NtTerminateProcess" error, go with "kb" that prints stack trace and "~* kp" to dump the whole stack.

*** This bug has been marked as a duplicate of bug 108368 ***