Bug 156634 - REPORTBUILDER: Crash in: rptxml::ORptExport::exportSectionAutoStyle(com::sun::star::uno::Reference<com::sun::star::report::XSection> const &)
Summary: REPORTBUILDER: Crash in: rptxml::ORptExport::exportSectionAutoStyle(com::sun:...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
7.5.5.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 156635 (view as bug list)
Depends on:
Blocks: Database-Reports-Builder
  Show dependency tree / graph
 
Reported: 2023-08-06 11:42 UTC by Michael
Modified: 2023-10-09 10:26 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: ["rptxml::ORptExport::exportSectionAutoStyle(com::sun::star::uno::Reference<com::sun::star::report::XSection> const &)"]

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael 2023-08-06 11:42:20 UTC 
This bug was filed from the crash reporting server and is br-5f9a7d03-065b-408a-974e-0b26e79fe871.
=========================================
Comment 1 Julien Nabet 2023-08-06 15:19:03 UTC 
*** Bug 156635 has been marked as a duplicate of this bug. ***
Comment 2 Julien Nabet 2023-08-06 15:19:52 UTC 
Could you provide minimum step by step process to reproduce this?
Comment 3 Michael 2023-08-06 17:56:00 UTC 
It appeared in Base. Report Builder. I was in the middle of defining a report and pressed 'Execute Report'.
Comment 4 Julien Nabet 2023-08-06 19:28:29 UTC 
(In reply to Michael from comment #3)
> It appeared in Base. Report Builder. I was in the middle of defining a
> report and pressed 'Execute Report'.

Does it happen at random or you can reproduce this any time? In the last case, could you be more specific about how to do this?
Comment 5 Michael 2023-08-07 15:29:16 UTC 
A similar crash has occurred a second time, see https://crashreport.libreoffice.org/stats/crash_details/959dc5a6-f66b-4c13-805f-70d64ba5ed6c

I both cases, a database report was open for editing. The report was changed at various places. It has not been saved before I pressed 'Execute Report'. 
The actual state of the database and actual definition of the report was lost due to the crash. 

I'm sorry I can't provide more details. I hoped the crash reports would provide the necessary details.
Comment 6 Julien Nabet 2023-08-07 17:02:47 UTC 
The last crash record is similar to previous.
Without a way to reproduce this, I don't know how to help but maybe some people will know.
Can't do anything here=>uncc myself.
Comment 7 Xisco Faulí 2023-09-11 12:28:29 UTC 
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 8 Michael 2023-09-11 14:54:03 UTC 
I'm sorry but I can't attach a document that exhibits the problem. Unfortunately the document involved is not available because a crash prevented me from saving it. The best information about the context of this bug is found in the crah report  br-5f9a7d03-065b-408a-974e-0b26e79fe871..
Comment 9 Stéphane Guillou (stragu) 2023-10-06 10:17:32 UTC 
Looking at the crashes with the same signature, looks like it hasn't happened so far since 7.5.6 or 7.6.1.

I'm wondering if those crash fixes might have something to do with it:

https://bugs.documentfoundation.org/buglist.cgi?list_id=1659353&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&resolution=NOTABUG&resolution=NOTOURBUG&resolution=INSUFFICIENTDATA&short_desc=crash&short_desc_type=allwordssubstr&status_whiteboard=target%3A7.6.1%20target%3A7.5.6&status_whiteboard_type=allwordssubstr

Michael, please make sure you update to the latest version (7.6.2.1) and let us know if it happens again. Setting to "needinfo" for the moment.
Much appreciated!
Comment 10 Michael 2023-10-06 14:53:30 UTC 
In the meantime I finished creating my database report. This means that the chances are not very high that I will encounter the problem again, as I do not currently use the functionality in question.
Comment 11 QA Administrators 2023-10-07 03:19:49 UTC Comment hidden (obsolete)
Comment 12 Stéphane Guillou (stragu) 2023-10-09 10:26:22 UTC 
OK, let's close as "insufficient data" as you won't be able to re-test to confirm the bug is gone.
In any case, we have this bug linked to the crash signature, so it can be reopened if needed.
Thank you!