Bug 140965 - LIBREOFFICE 7.1 program crashes after activating (external) query update
Summary: LIBREOFFICE 7.1 program crashes after activating (external) query update
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.1.1.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Crash
  Show dependency treegraph
 
Reported: 2021-03-12 00:42 UTC by hawouters
Modified: 2024-10-08 03:16 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
this testfile with webquery's showed the crash error (163.50 KB, application/vnd.ms-excel)
2021-03-12 22:21 UTC, hawouters
Details

Note You need to log in before you can comment on or make changes to this bug.
Description hawouters 2021-03-12 00:42:11 UTC
Description:
LIBREOFFICE 7.1: After opening a worksheet with manny external webquery's the program crashes at activating the button "koppelingen bijwerken"(allow query update) in the upper yellow area.
LIBREOFFICE 7.05 is ok.

Steps to Reproduce:
1.Open a worksheet that contains about 10 external webquery's
2.press the button "allow update = bijwerken toestaan" in the upper yellow erea
3.

Actual Results:
program crashes. A continuing hourglass is running for ever.Program doesnt react at all. Is dead.

Expected Results:
Update all Webquery's


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
versie 7.1.1.
Comment 1 raal 2021-03-12 06:48:27 UTC
Please attach test file. Thank you.
Comment 2 hawouters 2021-03-12 22:21:58 UTC
Created attachment 170449 [details]
this testfile with webquery's showed the crash error
Comment 3 pavlog 2021-04-11 18:26:30 UTC
I can reproduce it in

Version: 7.2.0.0.alpha0+ (x64)
Build ID: ecb916667b633f8647790e040226b093760e6cfe
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL

Version: 7.1.2.2 (x64) / LibreOffice Community
Build ID: 8a45595d069ef5570103caea1b71cc9d82b2aae4
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL
Comment 4 Xisco Faulí 2021-06-15 09:24:04 UTC
I can't reproduce it in

Version: 7.2.0.0.beta1+ / LibreOffice Community
Build ID: d376297c643785564e7bda1a74b573c35ade6cb8
CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: x11
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 5 Xisco Faulí 2021-06-15 09:28:14 UTC
Nor in

Version: 7.1.4.2 (x86) / LibreOffice Community
Build ID: a529a4fab45b75fefc5b6226684193eb000654f6
CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win
Locale: ar-DZ (es_ES); UI: es-ES
Calc: threaded

@hawouters@hotmail.com, please paste the info from Help - About LibreOffice
Comment 6 Matt K 2024-03-10 00:52:34 UTC
(In reply to Xisco Faulí from comment #5)

No repro using:

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 1b1c51ff9e3fe3356a0ba259a0c3e9cfccda0089
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

Marking NEEDINFO
Comment 7 QA Administrators 2024-09-07 03:18:42 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2024-10-08 03:16:51 UTC
Dear hawouters,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp