Details
-
Bug
-
Resolution: Won't Do
-
P2: Important
-
None
-
5.13.0
Description
Creating Android service for each remote backend (generated with ivigenerator server_qtro template), cause significant overhead in RAM (Android service without any logic consume around 6 MB on Android 9, X86). To overcome that problem Android services can be grouped to one process.
Android system enables grouping services into one process in operating system by setting the same "android:process" property for multiple services in Manifest file:
... <service android:process=":process1" android:name=".Service1"> ... </service> ... <service android:process=":process1" android:name=".Service2"> ... </service> ...
The server_qtro template code, contains a singleton class Core. The same singleton class is generated for all services, making it impossible for us to initialize more than one service within a single process.
Attachments
Issue Links
- depends on
-
QTBUG-78009 Android services grouped into one process do not start
- Closed
- relates to
-
QTBUG-99073 Add support for multiple qface files in QFACE_SOURCES
- Reported
-
QTBUG-99085 Replace the autogenerated Core class with something more smart
- Closed
For Gerrit Dashboard: AUTOSUITE-1161 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
271264,1 | ivigenerator: Fix naming of the "core" class in the qtro_server templates | 5.13 | qt/qtivi | Status: ABANDONED | -1 | 0 |