[webapp-container] AP tests crash when state saver is enabled

Bug #1372943 reported by Alexandre Abreu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
webbrowser-app
Fix Released
High
Jean-Francois Moy

Bug Description

Based on the non yet lander branch:

https://code.launchpad.net/~abreu-alexandre/webbrowser-app/remove-session-storage

that disables the session storage bits from the container, when subsequently enabling the StateSaver to take over part of the work done by the session storage, AP tests produce a crash when being run on the device.

In order to repro it:

- take the branch above (unless it has landed in the meantime),
- add

StateSaver.properties: "url"
StateSaver.enabled: true

to src/app/webcontainer/WebApp.qml ,

- compile on the device & run the AP tests for the container on the device

autopilot3 run webapp_container

there should be a crash file in /var/crash.

TO BE NOTED:
----------------------

- The tests actually succeed, the crash happens as the app is being closed,
- The stack trace (at least for me) was corrupted,
- There seem to be a race somewhere since, adding a bit of delay in any AP test that maked the container crash (even a sleep of 1sec) makes the issue go away,
- The state saver does quite a bit in terms of binding to the app lifecycle, creating an archive for the state backups, etc. as the app is being launched and does some things also (cleanup archive file, save archive file, etc.) as the app is being closed, and might end up in a messy state since the tests do involve a very quick run of the app,

Changed in webbrowser-app:
assignee: nobody → Jean-Francois Moy (jfmoy)
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Jean-Francois Moy (jfmoy) wrote :

After building and installing the webapp_container and running the autopilot tests on rtm (r52) platform, crash files were created in /var/crash. The stack trace is unfortunately incomplete:

#0 0xb6c95e70 in QMapDataBase::freeTree(QMapNodeBase*, int) ()
   from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5

However, after updating to rtm-proposed (r59) and following the same steps, no crash files were created and the tests run fine.

Revision history for this message
Jean-Francois Moy (jfmoy) wrote :

This was due to #1363112 that has now been fixed. The tests now run perfectly and no crash file is generated.

Changed in webbrowser-app:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.