[Qt-creator] QtCreator 4.6 - constant, high CPU usage

2018-04-13 Thread Jakub Narolewski
Thank you for the link to the Jira task, Alessandro. I now believe I can reproduce this 100% of the time. I have added a comment in the Jira. From: Alessandro Portale Sent: 13 April 2018 16:15 To: Jakub Narolewski; qt-creator@qt-project.org Subject: AW: QtCreator 4.6 - constant, high CPU usage

[Qt-creator] Lightbulb everywhere

2018-04-13 Thread Jason H
I'm trying out the new clazy and fixit support in 4.6. I have a few observations, I'm hoping people can suggest how to fix them. (No pun intended). Most of these are not QtCreator's fault, but some are. The question for those are how does QtC help manage them? 1. Header guards are not

Re: [Qt-creator] QtCreator 4.6 - constant, high CPU usage

2018-04-13 Thread Alessandro Portale
Hi Jakub, there were reports about Qt Creator occupying one CPU core for no obvious reason. Here is the Jira task: https://bugreports.qt.io/browse/QTCREATORBUG-19458 It would be great to gather more information about it. Thank You, Alessandro Von:

[Qt-creator] QtCreator 4.6 - constant, high CPU usage

2018-04-13 Thread Jakub Narolewski
Hello :] I'm having a weird problem with newest Creator update. QtC seems to spin some heavy-duty thread on one of CPU cores on all my machines. On my six cored AMD CPU I see it taking 16% of total processing power [as reported by Windows' Task Manager]. I notice it every time due to my

Re: [Qt-creator] Multiple Android APK support?

2018-04-13 Thread Nikos Chantziaras
When uploading the x86 build, the site replaces the previous build unless you select "Retain" for it. Once you do that, it does seem to work and both APKs seem to be active. You get a warning though about "Differentiating APK details", but it's not a hard-error. But it seems the site

Re: [Qt-creator] Memory usage of Qt Creator

2018-04-13 Thread Carel Combrink
Hi, I work on a quite large application and my clangbackend crashes often due to running out of memory. I am using Qt Creator 4.6.0 [Qt 5.10.1 (MSVC 2015, 32 bit)] Thus if the clangbackend reaches about 1.4GB of RAM it crashes, then starts growing again, rinse and repeat... Switching to 64 but

Re: [Qt-creator] Memory usage of Qt Creator

2018-04-13 Thread Aleksey Kontsevich
Clean QtC 4.5.2 takes 60 MB for me. -- Best regards,AlekseyLinked in https://www.linkedin.com/in/alekseykontsevich   13.04.2018, 13:32, "timur.kris...@gmail.com" :Hi,Just noticed that with the latest version of Qt Creator the memoryusage numbers went up.Currently I get

[Qt-creator] Memory usage of Qt Creator

2018-04-13 Thread timur . kristof
Hi, Just noticed that with the latest version of Qt Creator the memory usage numbers went up. Currently I get ~400MiB for qtcreator and ~450MiB for clangbackend. This seems to slowly go down after I close some source files, though it takes time (guess it keeps them in cache for a while). Are

Re: [Qt-creator] clang-format config for Qt coding style

2018-04-13 Thread Eike Ziller
> On 13. Apr 2018, at 11:11, Kari Oikarinen wrote: > > > > On 13.04.2018 11:59, timur.kris...@gmail.com wrote: >> Hi, >> I'm working on a project which uses the Qt coding style. >> Does you guys have a .clang-format config file for this style which I >> can use with Qt

Re: [Qt-creator] clang-format config for Qt coding style

2018-04-13 Thread Kari Oikarinen
On 13.04.2018 11:59, timur.kris...@gmail.com wrote: Hi, I'm working on a project which uses the Qt coding style. Does you guys have a .clang-format config file for this style which I can use with Qt Creator's Beautify plugin? There is one at

[Qt-creator] clang-format config for Qt coding style

2018-04-13 Thread timur . kristof
Hi, I'm working on a project which uses the Qt coding style. Does you guys have a .clang-format config file for this style which I can use with Qt Creator's Beautify plugin? Thanks, Timur ___ Qt-creator mailing list Qt-creator@qt-project.org

Re: [Qt-creator] Multiple Android APK support?

2018-04-13 Thread Ivan Donchevskii
As far as I know store expects both in the same apk. So as I understand you suggest having two different versions in store for different platforms? That may work. Thanks for one more workaround :) Regards, Ivan From: Qt-creator