https://bugs.documentfoundation.org/show_bug.cgi?id=73049
--- Comment #43 from Markus Mohrhard <markus.mohrh...@googlemail.com> --- (In reply to andis.lazdins from comment #42) > (In reply to Joel Madero from comment #41) > > Markus is one of our most experienced developers - closing. > > > > His point was that you were describing a separate issue from how this bug > > starts: > > > > "Libreoffice Calc module constantly crashes on opening particular complex > > ods file containing array formulas." is not the same as "just tried to work > > with 8 MB calc while without any formulas, which takes about 30 sec to open > > for OpenOffice.org." > > > > As for the rest of your rant, I'll avoid commenting beyond saying...I do a > > lot more with Calc than just school exercises.... > > > > Feel free to open a new clean bug that is specific to the issue that you > > describe in your latest (prior to rant) comment. > > It is very sad that you cannot understand, that for many people it can be > the same that "Libreoffice Calc module constantly crashes on opening > particular complex ods file containing array formulas" and "just tried to > work with 8 MB calc". It is very sad that formulation of comment is used as > an argument to close report on serious regression. If it is so important I > can repeat that I have the same issue: > terminate called after throwing an instance of 'std::bad_alloc' > what(): std::bad_alloc > > with the same files I had initially, but it is not any more 100% "success". > I don't have time to waste for testing if the "improvement" works on other > computers. Luckily openoffice.org still exist and we can use it for > production. Will try one more time, when we will change computers or > libreoffice will change something in attitude. > > Good luck! As I mentioned you should open a new bug report for each of the issues. We have a one issue, one bug report policy and as soon as you start using the same bug report for unrelated issues it is better to close the report and open new ones. This policy helps developers and QA person as it is otherwise never clear what a bug fix actually tried to fix. I did not say anywhere that your reports are invalid just that this report in its current form with many unrelated issues has become too confusing. We need to start with a clean report for each issue and let a developer decide if they might be duplicates. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
