Have you tried debugging with a debugger (run the app under gdb and
examine the backtrace when it gets stuck)? That seems to be the obvious
first step to me.
Cheers,
-Slava
> We debugged a failure to initiate destruction further. As suggested
> by @wdehoog, I added
>
> Connections {
> target: __quickWindow
> onClosing: console.log("....")
> }
>
> to ApplicationWindow. This one does get called during app closure,
> without further propagation over to destruction of items.
>
> Any ideas on how to debug it further?
>
> Rinigus
>
>
>
> On Sat, Sep 8, 2018 at 4:24 PM rinigus <rinigus.git at gmail.com
> <mailto:rinigus.git at gmail.com>> wrote:
>
> Hi,
>
> I am working on Pure Maps - a fork of @otsaloma's map
> applications. As a background: Its a Python app, with pyotherside
> used for QML/Python interaction. Its also using Mapbox GL widget
> that I wrote on the basis of Mapbox GL QtLocation plugin.
>
> I am facing a problem which I don't know how to solve, hence
> asking for help. Namely, Pure Maps sometimes does not shutdown
> cleanly after closure by the user. Namely, when app is closed in
> GUI (I presume close guesture or touching X in SFOS overview
> mode), the process stays. Same if the app is started from terminal
> - if the shutdown was unsuccessful, terminal prompt does not
> return after closing the program.
>
> And here were the mystery starts. With the suspicion that maybe
> some python call is hanging, the printouts were added before and
> after Python calls (through QML Python wrapper). Regardless to
> whether the app was shutdown cleanly or was left hanging, the
> calls (sync or async) always returned.
>
> I have added printout statements in Component.onDestruction for
> key QML items in the app and could see that, when the app hangs,
> none of the onDestruction handlers were called.
>
> Hence the question, what could cause Silica app to refuse starting
> destruction cascade?
>
> This issue is mainly reported by J1 users and I had a great help
> from @pichlo with debugging it. Sometimes, we observed OOM killing
> of other app during the navigation. So, I presume, the device is
> under significant RAM pressure. But still, I am rather blank on
> where to debug it further and what could cause such behavior.
>
> For the record, haven't seen this on my device (onyx).
>
> Rinigus
>
>
>
> _______________________________________________
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscribe at lists.sailfishos.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.sailfishos.org/pipermail/devel/attachments/20180909/d0e94b52/attachment.html>