Description: ~17 page document, including ~10 tables and two paper sizes (mixed portrait and landscape). After crash, did not try to recover. Attempt to re-open the document yielded crash note and offer to restart in safe mode. Steps to Reproduce: 1.Print preview (Ctrl-Shft-O) 2. 3. Actual Results: Crashed. Expected Results: Should not crash. Reproducible: Didn't try User Profile Reset: No OpenGL enabled: Yes Additional Info: Presumably it is related to the file. Version: 6.0.6.2 (x64) Build ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: en-ZA (en_US); Calc: group https://gerrit.libreoffice.org/gitweb?p=core.git&a=log&h=0c292870b25a325b5ed35f6b45599d2ea4458e77
Created attachment 144631 [details] File that crashed This is the document that crashed when Print Preview was invoked. However, subsequent attempt to reproduce crash unsuccessful; that is, no problem afterwards.
I had dump using procdump with this file with 6.0.6 and 6.1.1 and master on first load but not anymore. ucrtbase.dll: FOLLOWUP_IP: ucrtbase!_wsopen_nolock+cc 6b5b0e92 8bf8 mov edi,eax But if no repro steps we can only close.
I can't reproduce the crash Versió: 6.0.6.2 ID de la construcció: 1:6.0.6-0ubuntu0.16.04.1 Fils de CPU: 4; SO: Linux 4.15; Renderitzador de la IU: per defecte; VCL: gtk3; Configuració local: ca-ES (ca_ES.UTF-8); Calc: group Versión: 6.1.0.3 Id. de compilación: efb621ed25068d70781dc026f7e9c5187a4decd1 Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; Configuración regional: es-ES (es_ES); Calc: group threaded Version: 6.2.0.0.alpha0+ Build ID: 4b5fcd417587cfb9e6d8b61ecb037ab165eeb5b9 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: threaded To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
I completely agree with the resolution, as I could not reproduce it either. I was just trying to report as suggested, with whatever info I could gather, in the remote hope that the case might enlighten something. As it happened, it merely cost you time. Thanks for your effort. John
Ok, Let's close this as RESOLVED INSUFFICIENTDATA for the time being. Don't hesitate to open it again if you find the way to reproduce it. Anyway, thank you very much for reporting this issue.