https://bugs.documentfoundation.org/show_bug.cgi?id=105231
Bug ID: 105231
Summary: Null-messag exceptions or other unexplained errors
(memory corruption?) after many operations
Product: LibreOffice
Version: 5.3.0.0.beta2
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Calc
Assignee: [email protected]
Reporter: [email protected]
Created attachment 130296
--> https://bugs.documentfoundation.org/attachment.cgi?id=130296&action=edit
test case spreadsheet (t.ods)
I use Basic macros which copy & paste from one sheet to another. Sometimes the
paste does not seem to do anything, or at least doesn't copy formulas. I had
to write Basic code to check the result where a formula is expected, and if no
formula is found then repeat the copy & paste (with a warning), which then
succeeds. Again, this occurs fairly often but unpredictably and, sadly, not
repeatably.
-> The bug might somehow depend on the state of the heap, or perhaps the
specific virtual addresses of dynamically-loaded modules (which are randomized
and vary between process invocations). I suspect this because sometimes I
load a spreadsheet and immediately run the macro and it fails; but if I exit
without saving and repeat the same steps, it does not fail. So it depends on
some state which isn't part of the spreadsheet or its macros.
Anyway, I tried and failed to create a test case for that particular problem.
But in the process, I found numerous seemingly-bogus errors and exceptions
which occur after a large number of operations. One is a "null message"
exception message from a call to <row object>.removeByIndex()
BASIC runtime error.
An exception occurred
Type: com.sun.star.uno.RuntimeException
Message: .
Even if the the parameters(offset and count) were invalid, the exception
message should say _something_ useful. So I suspect the exception is bogus,
i.e., not due to my macro logic error, or if it is, then the runtime system is
confused enough that it could not show a useful error message.
STEPS TO REPRODUCE:
1. Download the attached demo spreadsheet (t.ods) and the test data file
2. Place the test data in /tmp/testdata.csv
That path is hard-coded in the spreadsheet, so it has to be there
3. Open the spreadsheet, and enable macros when prompted (or in
Tools->Options->Security->MacroSecurity)
4. Repeatedly click the black "Disc+Reload" button
RESULTS: Eventually (after 10-20 iterations), a "null message" exception will
occur, or some other unexplain(able) error.
I'm sorry this isn't cleaner, but I'm convinced there is some kind of
corruption which results in incorrect behaviour, even if just the suppression
of diagnostic messages.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
