qmlplugindump running at 100% cpu
Bug #1300957 reported by
Pat McGowan
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-webapps-qml (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I noticed my fan running, and saw qmlplugindump using 100%
I killed qtc and it went away.
I had been build and running a simple console app prior to that
Related branches
lp:~abreu-alexandre/unity-webapps-qml/fix-issues-uncovered-by-qmlplugindump
- PS Jenkins bot (community): Approve (continuous-integration)
- WebApps: Pending requested
-
Diff: 1031 lines (+453/-253)27 files modifieddebian/unity-webapps-qml-autopilot.install (+1/-0)
src/Ubuntu/UnityWebApps/UnityWebApps.qml (+19/-1)
src/Ubuntu/UnityWebApps/UnityWebAppsUtils.js (+4/-0)
src/Ubuntu/UnityWebApps/plugin/plugin.pro (+0/-2)
src/Ubuntu/UnityWebApps/plugin/qml-plugin.cpp (+0/-2)
src/Ubuntu/UnityWebApps/plugin/unity-webapps-app-infos.cpp (+2/-1)
src/Ubuntu/UnityWebApps/plugin/unity-webapps-app-model-filter-proxy.cpp (+0/-76)
src/Ubuntu/UnityWebApps/plugin/unity-webapps-app-model-filter-proxy.h (+0/-87)
src/Ubuntu/UnityWebApps/plugin/unity-webapps-app-model.cpp (+1/-1)
src/Ubuntu/UnityWebApps/plugin/unity-webapps-app-model.h (+1/-1)
tests/integration/autopilot/autopilot.pro (+7/-2)
tests/integration/autopilot/data/all-in-same-folder/script.user.js (+1/-0)
tests/integration/autopilot/data/all-in-same-folder/webapp-properties.json (+8/-0)
tests/integration/autopilot/data/unity-webapps-normal/manifest.json (+7/-0)
tests/integration/autopilot/data/unity-webapps-normal/script.user.js (+1/-0)
tests/integration/autopilot/data/unity-webapps-with-altered-ua-string/manifest.json (+8/-0)
tests/integration/autopilot/data/unity-webapps-with-altered-ua-string/script.user.js (+1/-0)
tests/integration/autopilot/qml/FullWebViewApp.qml (+48/-23)
tests/integration/autopilot/qml/WebviewBackendOxide.qml (+87/-0)
tests/integration/autopilot/qml/WebviewBackendWebkit.qml (+19/-0)
tests/integration/autopilot/qml/message-server.js (+29/-0)
tests/integration/autopilot/unity_webapps_qml/emulators/__init__.py (+0/-7)
tests/integration/autopilot/unity_webapps_qml/tests/__init__.py (+66/-31)
tests/integration/autopilot/unity_webapps_qml/tests/fake_servers.py (+70/-0)
tests/integration/autopilot/unity_webapps_qml/tests/test_installedWebapp.py (+59/-0)
tests/integration/test-server.py (+0/-18)
tools/qml-launcher/qml-launcher.cpp (+14/-1)
Changed in qtcreator-plugin-ubuntu: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in qtcreator-plugin-ubuntu: | |
assignee: | nobody → Zoltan Balogh (bzoltan) |
tags: | added: qa-daily-testing rtm14 |
no longer affects: | unity-webapps-qml |
no longer affects: | qtcreator-plugin-ubuntu |
To post a comment you must log in.
It seems that qmlplugindump is "stuck" when dealing with the Ubuntu.UnityWebApps plugin:
#0 0x00007f06d83e04c0 in UnityWebappsApp ModelFilterProx y::sourceModel( ) const () from /usr/lib/ x86_64- linux-gnu/ qt5/qml/ Ubuntu/ UnityWebApps/ libUnityWebApps .so ModelFilterProx y::qt_metacall( QMetaObject: :Call, int, void**) () x86_64- linux-gnu/ qt5/qml/ Ubuntu/ UnityWebApps/ libUnityWebApps .so :read(QObject const*) const () from /usr/lib/ x86_64- linux-gnu/ libQt5Core. so.5 ed48, init=<optimized out>, fini=<optimized out>, rtld_fini= <optimized out>, end=0x7fffe7dee d38) at libc-start.c:287
#1 0x00007f06d83e583d in UnityWebappsApp
from /usr/lib/
#2 0x00007f06ea2c34a1 in QMetaProperty:
#3 0x0000000000407dac in ?? ()
#4 0x00000000004095ac in ?? ()
#5 0x0000000000406af9 in ?? ()
#6 0x00007f06e9722ec5 in __libc_start_main (main=0x405190, argc=5, argv=0x7fffe7de
stack_
#7 0x0000000000406ef4 in ?? ()