This bug was filed from the crash reporting server and is br-de650db9-d246-4717-a64e-d00b5315a2bd. ========================================= Working with a .osd that has worked for several months. Crash is triggered by clicking on the drop down triangle in a page-field in an existing pivot report. The data source content on another tab was changed (pasted CSV import, deleted rows that contained header) right before going to this tab. Reproducible :-) since I just did this twice. Recovery worked fine. Also triggered by selecting "Update" on the pivot report pivot source is a named area The problem is also triggered in "safe mode" It does not help to delete the inserted data. It does not help to reduce the named area size (from >800 rows to 20 rows) More pivot reports look at the same named area, the crash occurs no matter which report you try to update data Creating a new pivot report, at first works (computes a total) but adding rows to the pivot table makes it crash. Creating a new workseet, and building a report from scratch also triggers the crash. I just upgraded to version 5.3.2.2, I think I had 5.2.xxx before
I had two users logged in at the time when I upgraded. I usually never restart my computer, only go into hybernation. By logging out of both accounts and restarting the computer, the problem was solved.
(In reply to Peer Sommerlund from comment #1) > I had two users logged in at the time when I upgraded. I usually never > restart my computer, only go into hybernation. > > By logging out of both accounts and restarting the computer, the problem was > solved. You mean you can no longer reproduce the crash initially reported ?
That is correct.
Setting to RESOLVED WFM