Created attachment 61265 [details]
rtf document, causing CRASH
Immediate crash in opening RTF document.
Steps to reproduce:
1. Try open attached file
Document is opened
Platform (if different from the browser):
Browser: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0
Created attachment 61305 [details]
bt with symbols + console message
On pc Debian x86-64, I reproduced the problem on 3.5 branch and master (both updated today).
I attached the bt with symbols (+ console messages) from master.
Thanks for reporting this bug, but it's not BASIC, but Writer issue.
Created attachment 62356 [details]
Bug 49666 - WinDbg session
Build ID: own W7 debug build
Windows 7 Professional SP1 64 bit
Crash while loading.
Attached full WinDbg session with mini dump file loaded generated by procdump soffice.bin -h.
On Pc Debian x86-64, with master sources updated today, I don't reproduce the crash anymore but I had "General Input/output error" popup.
Also crashes in v188.8.131.52 (build id: 24b32b4-b87ec2e-85c8e98-87a4e20-9a1b8c1) under Windows 7 (x86_64).
Same RTF that crashes v184.108.40.206 does NOT crash LODEV v3.6
Created attachment 63853 [details]
RTF file containing image data and tables, with internal positioning and scaling control data.
This file crashes v220.127.116.11, and does not render correctly in v3.5.4 or LODEV v3.6
File correctly renders in IBM Lotus Symphony and Microsoft Word.
don't pile up different rtf documents that crash/render incorrectly in the same bug, write different ones for each.
I am having the same problem! I'm tested v3.5.4, v.3.5.5 and v18.104.22.168rc
22.214.171.124 doesn't crash on the original .rtf anymore, although it does fail to load, which I guess is acceptable as the format is busted.
If there are outstanding rtf crashers, please use different bugs for them.
Latest crash report points this document out once again.
Seems the problem is that the bugdoc contains a shape with type 75 (ESCHER_ShpInst_PictureFrame), which also has a shape text. Looks like this is an RTF which is generated by some 3rd-party tool: Word can open it, but it doesn't show the text on the picture frame, either -- and if I try to save it as RTF again, it crashes. ;-)
So, let's just ignore the shape text for picture frames at RTF import time as well, that should avoid the crash.
Miklos Vajna committed a patch related to this issue.
It has been pushed to "master":
fdo#49666 RTF import: fix crash on picture frame with shape text
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
I don't see the problem on -4-1, so closing without backporting.