SalAbort:Unspecified application error

[di liu]

>
> Does "more times" here mean that it takes longer now than previously
> until the problem shows up? Or is it pretty much unchanged for you?
>
> Is that with experimental mode enabled or disabled in the app settings?
>

I am so sorry,I made a mistake (I made some local changes but did not
restore the code completely which interferes the test result.)
After my initial test(on the same devices) the crash disappeared.
I will continue to test this issue on different devices and scenarios to
make sure it be fixed completely

Yes, that's most likely.
> The one from https://gerrit.libreoffice.org/c/core/+/133581 is also
> called further down in the stack from there and was clearly showing up
> in the memory profile.
>
> The app was working fine with the sample file in non-editing mode  for
> me with that hack in place in a quick test.
> But it's well possible that there are more leaks elsewhere.
>


 Yeah,thank you so much for all you do.

Michael Weghorn <m.weghorn at posteo.de> 于2022年4月29日周五 18:54写道：

> >     Is that file confidential or can it be shared publicly (attached to a
> >     Bugzilla ticket)? (I can't read most of the text in it. :-))
> >
> >
> >  The file is not confidential and can be shared publicly (haha，The text
> in it is chiness)
>
> Great, thanks.
>
>
> On 29/04/2022 12.07, di liu wrote:
> >     Ok, I will make a try (recompile the source code will spend me
> >     hours... )
> >
> >
> > Unfortunately it's also crash with same error when i swipe up and down
> > more times.
>
> Does "more times" here mean that it takes longer now than previously
> until the problem shows up? Or is it pretty much unchanged for you?
>
> Is that with experimental mode enabled or disabled in the app settings?
>
> > I suppose the memory leak maybe exit in this method
> > "desktop/source/lib/init.cxx -> doc_paintTile".Because every time i
> > swipe the screen the java code will call this method to paint tile where
> > crash was happened
>
> Yes, that's most likely.
> The one from https://gerrit.libreoffice.org/c/core/+/133581 is also
> called further down in the stack from there and was clearly showing up
> in the memory profile.
>
> The app was working fine with the sample file in non-editing mode  for
> me with that hack in place in a quick test.
> But it's well possible that there are more leaks elsewhere.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice/attachments/20220430/55d7fbe6/attachment.htm>