Steps how to reproduce with Version: 6.1.0.3 (x64) Build-ID: efb621ed25068d70781dc026f7e9c5187a4decd1 CPU-Threads: 4; BS: Windows 6.1; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group threaded my default user profile: 1. Open new writer document from Start Center 2. From Gallery add "popcorn_1" go document 3. 'Rightclick popcorn_1 -> Insert Caption -> Type some characters for Caption text -> [OK] bug: somewhere in Step 3 LibO will crash. 😥 Additional Info: a) Happens with any picture I tested b) also crashes in safe mode c) no crash with 6.0 d) crashreport.libreoffice.org/stats/crash_details/a60b1c14-05f5-4b27-bc9c-7f348c68b65c e) Crash reason: EXCEPTION_ACCESS_VIOLATION_READ
f) Crash also happens with newly Created User Profile. I simply renamed my normal user profile folder, so that LibO created a new User Profile when it started. Crash in Step 3 after 'Insert popcorn_1' I will try a separate PC (WIN10) later.
I can not confirm with Version: 6.2.0.0.alpha0+ Build ID: 1da9b165b9c47f52db97fe70fe3e83626e580cdd CPU threads: 4; OS: Windows 6.1; UI render: default;
I can't reproduce it in Version: 6.2.0.0.alpha0+ Build ID: 18e20676024baecaf5719139f80f053f5f1e784a CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: threaded Only happens with popcorn_1 ?
On pc Debian x86-64 with master sources updated yesterday or with LO Debian package 6.1.0.3, both with gen rendering, I don't reproduce this. Noticing fontcharmap in crashreport, could you indicate which font do you use by default? Also, do you use some special/accentuated characters in the caption or just plain ASCII?
(In reply to Julien Nabet from comment #4) Crash often happens before I start typing. Al the same with server installation (and new User Profile) Any hints from crash reports?
According to LO versions, the stacktraces are quite different. I focused on 6.1 branch and found there were 2 or 3 different traces. Each time, it concerns some instruction with "new" and seems related to font. Just my opinion but wonder if it could be a bug in font management (LO Windows only) which exhausts RAM. Rainer: do you have only fonts from Windows OS + MsOffice and LO fonts or do you have other fonts? If any specific and just for the test, would you mind to remove them temporarily and give it a new try? If you got extra time, you may also give a try to a daily build (see https://dev-builds.libreoffice.org/daily/master/). Khaled/Tomaž: thought you might be interested in this one since it seems related to fonts.
Issue not reproduced with: Version: 6.1.1.1 (x64) Build ID: 2718b4a18dfcc6a54ebe5f7b801ee7a47fa81e0c CPU threads: 4; OS: Windows 6.3; UI render: default; Locale: en-US (en_US); Calc: CL
@Rainer Bielefeld, Do you still reproduce it with LibreOffice 6.1.1.1 ?
Please test with newer version. Thank you
Some tests with server installation of Version: 6.3.0.0.alpha0+ and newly createdUser Profile Build ID: 7f4600f6da54daaeb0d566c978a7ec60a50c9fbd CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-02-08_05:58:13 Locale: de-DE (de_DE); UI-Language: en-US Calc: CL Not Reproducible. WFM for now!