When opening a new spreadsheet and clicking the diagram button to insert a diagram Calc exits and recovery dialog appears. This happens with 22.214.171.124.beta1 and does not happen with 126.96.36.199 build. This is on Windows 7 using Estonian language should it make any difference.
When you say "diagram button" what button are you referring to? What's the actual label of the button?
I can not confirm with Version: 188.8.131.52.alpha0+
Build ID: e841dd17a4fb9ba558bcbea5cde5ec90061c1313
TinderBox: Win-x86@42, Branch:master, Time: 2014-11-29_23:46:43
With confirmation marking as NEW - setting to Highest as it's a regression crasher caught early in the cycle. Adding to 4.4 MAB tracker.
Oops, I think the correct term would be chart in English. The one with pie chart icon on it. In Estonian its labeled as "Diagramm".
On pc Debian x86-64 with master sources updated yesterday, I don't reproduce this.
merike: for the test, could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows) and give a new try?
Joel: do you mean you reproduced it?
No but raal did and is pretty active in QA so I trust the reproduction :)
(In reply to Joel Madero from comment #3)
> With confirmation marking as NEW - setting to Highest as it's a regression
> crasher caught early in the cycle. Adding to 4.4 MAB tracker.
Where did you see the confirmation? I only see a can not confirm from him.
Crap I misread - setting to UNCONFIRMED and removing from MAB. Sorry!
Yes, I did try renaming /user in AppData/Roaming/LibreOfficeDev (or a very similar name, not looking at it right now) and it still crashed after recreating that folder before my eyes. I also gave it a try in a Win7 virtual machine I have to see if it's only happening on one setup and it happened there too. Said virtual machine had never had dev build before so the profile had to be created for the first time.
Hi Merike, could you try without your language pack. Sometimes, incomplete translations give strange behaviors.
I don't reproduce using Version: 184.108.40.206.alpha0+
Build ID: 317b5bc5f801135b027e02d5acfc407cc2d05689
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2014-12-01_00:15:34
Locale: fr_FR Ubuntu 14.10 - Sophie
I don't reproduce using
LO 220.127.116.11.beta1 Build ID: 9af3d21234aa89dac653c0bd76648188cdeb683e Locale: fr_FR
& Windows 7 Home Premium
It still crashes when using the beta version in English (US). Is there any way of getting more information out of it, stack trace or similar?
(In reply to merike from comment #12)
> It still crashes when using the beta version in English (US). Is there any
> way of getting more information out of it, stack trace or similar?
You will find useful information here:
Best regards. JBF
Sounds a little like bug 86820 which was a crash after inserting a chart via *right-clicking* on a toolbar menu. Was this crash with a "normal" left click on the "insert chart" button ?
(In reply to Caolán McNamara from comment #14)
> Sounds a little like bug 86820 which was a crash after inserting a chart via
> *right-clicking* on a toolbar menu. Was this crash with a "normal" left
> click on the "insert chart" button ?
I was using normal left clicking.
Also, I tried to get a trace from WinDbg but the symbol path http://dev-downloads.libreoffice.org/symstore/symbols from https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg#First_Time_Setup is a 403 and inaccessible?
Created attachment 110679 [details]
I was able to get the following out of WinDbg. Is it helpful in understanding why I crash? Additionally on one of the crashing machines I only crash when logged in remotely. The other is a virtual machine. This trace is from the former one.
What can be done to get someone knowledgeable to look at the trace I provided? beta2 also crashes for me. It obviously does not affect everyone but anyone affected cannot add or change charts which is a serious issue.
Just a heads up that I've reached out to the developer community to try to get someone to take a peak at your log. Hope that moves it forward. Thanks so much for your patience.
This is related to OpenGL. Did you enable OpenGL in the options? I don't recall exactly how the code looked like for beta1 but for RC1 and RC2 it should be that there are 2 settings that enable OpenGL. Please disable them right now as our OpenGL rendering is not stable enough yet.
I never specifically enabled OpenGL. It must've been enabled automatically then. Anyway 18.104.22.168 does not crash in a similar way.