"RuntimeError: Wrong Nr of events" executing the app-launch-profiler

Bug #1574779 reported by Sergio Cazzolato
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-ui-toolkit (Ubuntu)
New
Undecided
Unassigned

Bug Description

I am getting errors when running the lttng profiler for the apps: Calculator, music, Camera, Clock, Here, Gallery , Ebay

See the commands executed and the result here: http://paste.ubuntu.com/16053036/
I also tested with different parametes and always got the same error (sometimes it works)

To get the process to use, run ubuntu-app-triplet with the following names for each app.

calculator: com.ubuntu.calculator
music: com.ubuntu.music
camera: com.ubuntu.camera
clock: com.ubuntu.clock
here: com.nokia.heremaps
gallery: com.ubuntu.gallery
ebay: com.ubuntu.developer.webapps.webapp-ebay

For the following apps, the results are ok: Messaging, Web Browser, System Settings, Dialer, Address Book

Tags: performance
Revision history for this message
Zoltan Balogh (bzoltan) wrote :

The blind guess is that the sleep time is too short.

The tool works in a way that it starts the app and expects the first frame event. After the defined sleep time the app gets stoped. This error happens when the first frame is not drawn before the app gets closed. Try to use longer sleep. Like 10secs

Revision history for this message
Sergio Cazzolato (sergio-j-cazzolato) wrote :

I have used longer times (12s), I am gonna try with even longer ones to see if it is the solution.

Revision history for this message
Sergio Cazzolato (sergio-j-cazzolato) wrote :

Tried with 12 and 15 seconds and I got the same error.

tags: added: performance
Revision history for this message
Sergio Cazzolato (sergio-j-cazzolato) wrote :

These are the event I got when I executed the here app with command
profile_appstart.sh -u 127.0.0.1 -p 0000 -a com.nokia.heremaps_here_1.0.9 -c 10 -s 15

It is clear that the qtmir:firstFrameDrawn event is arriving twice. This app is the only one it is being executed in the device.

Processing event: qtmir:firstFrameDrawn with time 1466131228876304823
Processing event: qtmir:firstFrameDrawn with time 1466131234380455207
Processing event: app:invokeApplauncher with time 1466131244640037362
Processing event: qtmir:firstFrameDrawn with time 1466131249647493285
Processing event: qtmir:firstFrameDrawn with time 1466131254389996287
Processing event: app:invokeApplauncher with time 1466131266062964363
Processing event: qtmir:firstFrameDrawn with time 1466131270738460749
Processing event: qtmir:firstFrameDrawn with time 1466131275479211980
Processing event: app:invokeApplauncher with time 1466131287277920750
Processing event: qtmir:firstFrameDrawn with time 1466131292310432365
Processing event: qtmir:firstFrameDrawn with time 1466131297210752442
Processing event: app:invokeApplauncher with time 1466131308810520212
Processing event: qtmir:firstFrameDrawn with time 1466131313751826212
Processing event: qtmir:firstFrameDrawn with time 1466131319441808906
Processing event: app:invokeApplauncher with time 1466131330230824983
Processing event: qtmir:firstFrameDrawn with time 1466131335186896213
Processing event: qtmir:firstFrameDrawn with time 1466131339976596522
Processing event: app:invokeApplauncher with time 1466131351694725522
Processing event: qtmir:firstFrameDrawn with time 1466131356948870601
Processing event: qtmir:firstFrameDrawn with time 1466131361853824754
Processing event: app:invokeApplauncher with time 1466131373144023832
Processing event: qtmir:firstFrameDrawn with time 1466131377544375909
Processing event: qtmir:firstFrameDrawn with time 1466131382511673370
Processing event: app:invokeApplauncher with time 1466131394092874294
Processing event: qtmir:firstFrameDrawn with time 1466131399067710294
Processing event: app:invokeApplauncher with time 1466131415569112757
Processing event: qtmir:firstFrameDrawn with time 1466131420595585143
Processing event: qtmir:firstFrameDrawn with time 1466131425398448988

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.