qmlplugindump hangs at 100% CPU with qtorganizer5-eds
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-ui-toolkit (Ubuntu) |
Fix Released
|
High
|
Cris Dywan |
Bug Description
I'm trying to build UITK on Manta
Note I've installed the demo data with "phablet-
Trying to build the UITK package natively on my tablet, with "dpkg-buildpackage -us -uc -j4" it hangs just after all test complete. Checking processes, I see "qmlplugindump" is running at 100% CPU usage, and nothing happens.
I attached to the process and grabbed a backtrace - looks interesting:
Program received signal SIGINT, Interrupt.
0x4066e5dc in QMutex::unlock() () from /usr/lib/
(gdb) bt
#0 0x4066e5dc in QMutex::unlock() () from /usr/lib/
#1 0x431cc806 in QtOrganizer:
#2 0x43444062 in QOrganizerEDSEn
from /usr/lib/
#3 0x4344d0fa in RequestData:
#4 0x43443fac in QOrganizerEDSEn
#5 0x431cca54 in QtOrganizer:
#6 0x43441caa in QOrganizerEDSEn
#7 0x43441dac in QOrganizerEDSEn
#8 0x431d2e46 in QtOrganizer:
#9 0x431d2ee0 in QtOrganizer:
#10 0x40787a94 in QObjectPrivate:
#11 0x4078bfe0 in QObject::~QObject() () from /usr/lib/
#12 0x4313b174 in AlarmManager:
#13 0x409fa8ba in ?? () from /lib/arm-
#14 0x409e8634 in __libc_start_main () from /lib/arm-
#15 0x0000d70a in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Related branches
- PS Jenkins bot: Needs Fixing (continuous-integration)
- Tim Peeters: Approve
-
Diff: 64 lines (+9/-11)4 files modifiedmodules/Ubuntu/Components/deployment.pri (+1/-1)
modules/Ubuntu/Components/plugin/adapters/alarmsadapter_organizer.cpp (+6/-9)
tests/qmlapicheck.sh (+1/-1)
tests/unit/runtest.sh (+1/-0)
Changed in ubuntu-ui-toolkit: | |
assignee: | nobody → Zsombor Egri (zsombi) |
importance: | Undecided → High |
status: | New → Confirmed |
summary: |
- qmlplugindump hangs at 100% CPU usage, while building UITK on device + qmlplugindump hangs at 100% CPU with qtorganizer5-eds |
Changed in ubuntu-ui-toolkit: | |
assignee: | Zsombor Egri (zsombi) → Christian Dywan (kalikiana) |
Changed in ubuntu-ui-toolkit (Ubuntu): | |
assignee: | nobody → Christian Dywan (kalikiana) |
importance: | Undecided → High |
status: | New → Confirmed |
no longer affects: | ubuntu-ui-toolkit |
Changed in ubuntu-ui-toolkit (Ubuntu): | |
status: | Confirmed → Fix Released |
This is a known issue - it is caused by the EDS backend. It is not happening when that one is not installed (qtorganizer5-eds). We have a workaround we should apply whenever qmlplugindump is invoked build time.
The workaround is to set env var ALARM_BACKEND= "memory" . In that case alarm services won't instantiate EDS backend at all.