I have uploaded a test build of en-US AOO419-dev for macOS. I have confirmed on
my macOS11/BigSur VM that this version opens docx files w/ no problems, edits
and saves them, etc...
Please test:
http://home.apache.org/~jim/AOO-builds/
Cheers!
> On Dec 26, 2020, at 3:54 PM, Rory O'Farrell <[email protected]> wrote:
>
> On Sat, 26 Dec 2020 21:43:06 +0100
> Matthias Seidel <[email protected]
> <mailto:[email protected]>> wrote:
>
>> Hi Jim,
>>
>> Am 26.12.20 um 20:45 schrieb Jim Jagielski:
>>> So there is for sure a bug in AOO41X, but why it only seems to affect macOS
>>> BigSur is
>>> unknown. It is this:
>>>
>>>> diff --git a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
>>>> b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
>>>> index f4d6c56..2ca9b8f 100644
>>>> --- a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
>>>> +++ b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
>>>> @@ -195,7 +195,7 @@ VtableFactory::VtableFactory(): m_arena(
>>>> rtl_arena_create(
>>>> "bridges::cpp_uno::shared::VtableFactory",
>>>> sizeof (void *), // to satisfy alignment requirements
>>>> - 0, reinterpret_cast< rtl_arena_type * >(-1), allocExec, freeExec,
>>>> 0))
>>>> + 0, reinterpret_cast< rtl_arena_type * >(0), allocExec, freeExec,
>>>> 0))
>>>> {
>>>> if (m_arena == 0) {
>>>> throw std::bad_alloc();
>>> I *think* this solves the issue, and a quick-and-dirty compilation seems to
>>> indicate that, but
>>> I will double check.
>>>
>>> The question is: Does this warrant a full 4.1.9 release for ALL platforms?
>>> To my mind, it does.
>>
>> I will start a test build on Windows right now...
>>
>> We have a small Linux issue as well [1] and we can still put some minor
>> cherry-picks into this build.
>>
>> +1 for a 4.1.9
>>
>> Regards,
>>
>> Matthias
>>
>> [1] https://bz.apache.org/ooo/show_bug.cgi?id=128413
>
> I think all platforms should maintain the same version numbering.
>
> There are occasional but frequent reports on Forum of problems with tables in
> Writer causing crashes when they are extended to cover multiple pages; my
> usual advice is to limit tables to one page, and repeat the structure if
> needed on subsequent pages. This seems to work; I cannot comment from
> personal experience as my routine work does not involve Writer tables. If
> this proposed fix involves tables it may have cross-talk into the Windows and
> other platforms.
>
> --
> Rory O'Farrell <[email protected] <mailto:[email protected]>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> <mailto:[email protected]>
> For additional commands, e-mail: [email protected]
> <mailto:[email protected]>
