Summary: | Calc crashes during execution of macro in XLS spreadsheet | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Moritz Mühlenhoff <jmm> |
Component: | Spreadsheet | Assignee: | Caolán McNamara <caolanm> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | major | ||
Priority: | lowest | CC: | erack, jmadero.dev, libreoffice |
Version: | 3.5.2 release | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | BSA target:4.4.0 | ||
i915 platform: | i915 features: | ||
Attachments: | backtrace of where things go wrong |
Description
Moritz Mühlenhoff
2012-04-06 15:29:02 UTC
I have confirmed this as well. I have no clue if this will be addressed as it's so specific to a particular macro enabled page that I personally have no clue what it's intended purpose is. Markig as NEW and prioritzing: Major: I'm hesitant to mark this as Major but since it causes a crash, I'm going by my normal flowchart and marking it as so. Lowest: So specific that it's unlikely another user would have face this furthermore there is a workaround to just go slow. If someone could do a bt that would be nice, I may be able to do one tomorrow. Created attachment 107551 [details]
backtrace of where things go wrong
at the bottom of the stack we have m_aDataArray.clear() but *mile* up the stack in frame 110 we have... m_aDataArray.push_back(Item()); Item& rItem = m_aDataArray.back(); rItem.maString = m_pDocument->GetString(aAdr); so during the GetString the m_aDataArray is cleared, so rItem is no longer valid and we cannot assign to it anymore legally With the straightforward approach of http://cgit.freedesktop.org/libreoffice/core/commit/?id=deed6dcacd355ce84cada955887a31e7d8cb5fb1 it no longer crashes. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.