A .csv output from a data analysis program I've written (somewhat wide columns, lots of odd characters) can be opened in Calc... but crashes Calc every time as scroll about halfway through it. Same .csv file opens and operates just fine in OpenOffice.
Steps to Reproduce:
1. Open file (I will be attaching it in a moment)
2. Start scrolling down through file using either scroll bar or mouse wheel
3. Crashes for me about 1/2 way down
No error msgs at all. Calc crashes all the way back to the desktop, window totally gone. Restarting LO -does- display the "recovery" box and that does restore the session. But scrolling again causes catastrophic crash.
OpenOffice 4.1.5 under Win10 has no problems w/ same file.
User Profile Reset: No
There are no error msgs to share. LO takes crash back to desktop.
Created attachment 146006 [details]
HP laptop, 8GB core
I can't reproduce it in
Id. de compilación: 65905a128db06ba48db947242809d14d3f9a93fe
Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.;
Configuración regional: es-ES (es_ES); Calc: group threaded
Build ID: cd6dd8c6f3562cbccbc971b916c6a8933840ffeb
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
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present
Created attachment 146016 [details]
Screen import window
Attached a screenshot of the import window that imports fine for me.
Having strange characters can means the 'character set' it's not properly selected.
no repro in
Version: 22.214.171.124 (x64)
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard;
Gebietsschema: de-DE (de_DE); Calc:
maybe an OpenGL issue?
I have had another spreadsheet crash in Libre which opens fine in OpenOffice. I did follow the procedure for opening LO in Safe Mode as suggested to test whether config files were corrupted. No difference, still crashes immediately upon opening in Safe Mode.
could you please try:
- disable: Tools/Options.../LibreOffice/View [ ] Use OpenGL for all rendering
- disable: Tools/Options.../LibreOffice/OpenCL [ ] Allow use of OpenCL
- restart LO
- open *.csv file
if this does not help, please give us a detailed description,
including lo version from menu help/About LibreOffice
> No difference, still crashes immediately upon opening in Safe Mode.
does it crash without scrolling?
Happens to me with a multi-sheet spreadsheet.One sheet contains charts created a year ago in the version current then. When scrolled to view Libre Office crashes out and spreadsheet needs recovering. Can sometimes be avoided by jump-scrolling.
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker