Bug 112418 - Calling ImageMagick COM object from macro with more than two parameters results in exception
Summary: Calling ImageMagick COM object from macro with more than two parameters resul...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: notBibisectable, regression
Depends on:
Blocks: Macro-Windows
  Show dependency treegraph
 
Reported: 2017-09-16 01:09 UTC by Aron Budea
Modified: 2023-09-18 03:05 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aron Budea 2017-09-16 01:09:40 UTC
Download and install ImageMagick from [1]. There are lots of different versions, for 32-bit LibreOffice ImageMagick-7.0.7-2-Q16-x86-dll.exe should be good.
During installation make sure check box 'Install ImageMagick OLE Control' etc. is checked. Finally, restart your computer.

Start Writer, open the macro editor via Tools -> Macros -> Edit Macros.
The following macro code uses ImageMagick to flip the image in the first parameter horizontally, saving the result into the file in the last parameter (substitute valid file names).
Run the macro:


Sub Main
Set img = CreateObject("ImageMagickObject.MagickImage.1")
r = img.Convert("c:\input.png", "-flop", "c:\output.png")
End Sub


There is the following error:
"BASIC runtime error.
An exception occurred 
Type: com.sun.star.lang.IllegalArgumentException
Message: [automation bridge]UnoConversionUtilities<T>::createUnoSequenceWrapper 
The any does not contain a sequence!."

There's no error if the 2nd parameter is removed (then the image is just copied into the target file).

[1] http://www.imagemagick.org/script/download.php

Observed using LO 6.0 daily build (2017-09-14_00:10:31, f70e0ec6b3c61a7c7caa469949b0ac8016c89854) and 3.5.0.3 / Windows 7.
Doesn't occur with LO 3.3.0.
=> regression
Comment 1 Aron Budea 2017-09-16 01:11:59 UTC
The exception is thrown at the beginning of this function:
template<class T> UnoConversionUtilities<T>::createUnoSequenceWrapper(const Any& rSeq, VARTYPE elemtype)
https://opengrok.libreoffice.org/xref/core/extensions/source/ole/unoconversionutilities.hxx#1007

There's the following line:
varType = getElementTypeDesc(&aFuncDesc->lprgelemdescParam[i].tdesc);
https://opengrok.libreoffice.org/xref/core/extensions/source/ole/oleobjw.cxx#1805

For the first two parameters 'varType' is 12, but for the 3rd parameter it's 8204, and that's when it enters the sequence-related code path.
Comment 2 QA Administrators 2018-09-18 02:50:22 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2021-09-17 03:50:51 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2023-09-18 03:05:59 UTC
Dear Aron Budea,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug