The ONLY change to my system was moving from Xcode 9.4.1 to Xcode 10.1. When I 
stop the build the cmake process does go away along with the underlying ninja 
process (I used Ninja as the generator) but the all the clang processes are 
still going. I also went into the project settings for this project and 
replaced the default build command with "ninja". Now when I cancel the build 
all the processes stop. I also tried from the command line using "cmake --build 
. --target all" and let that spin up the 24 clang instances and then did a 
"ctrl-c" to kill the process and everything stopped like I would expect. So it 
looks like a strange interaction between QtCreator, CMake and Xcode 10.x.

--
Michael Jackson | Owner, President
      BlueQuartz Software
[e] mike.jack...@bluequartz.net
[w] www.bluequartz.net <http://www.bluequartz.net>

On 1/9/19, 3:14 AM, "Eike Ziller" <eike.zil...@qt.io> wrote:

    That sounds like https://bugreports.qt.io/browse/QTCREATORBUG-21428
    
    As I commented in that bug report, Qt Creator stops the build command (in 
your case cmake --build, Qt Creator doesn’t know about any processes that 
starts), first “nicely” and after a timeout “not so nicely”. I suppose when 
killing “not so nicely” the system might not care about subprocesses.
    Is the “cmake” process gone after you cancel the build?
    
    Is the behavior different for you with a previous Qt Creator version? I’m 
not aware of changes in Qt Creator in that regard.
    
    Br, Eike
    
    > On 9. Jan 2019, at 03:45, Michael Jackson <mike.jack...@bluequartz.net> 
wrote:
    > 
    > Just updated from Xcode 9.x to 10.1 on macOS 10.13.6 and using QtCreator 
4.8.0. My project is CMake based which means the build command is something 
like 'cmake --build . --target ALL'. After I start the build if I want to stop 
the build I usually hit the red square button to stop the build and before this 
would work just fine. I have now noticed that the build keeps going (all my 
CPUs are pegged at 100%). I have to drop to a terminal and do "killall clang" 
to get them to stop. This happens on both a Mac Pro (2012) and a 2013 MacBook 
Pro. Both running macOS 10.13.6 and Xcode 10.1. CMake version is 3.13.0 on both 
machines.
    > 
    > Has anyone else seen this type of behavior?
    > 
    > Thanks
    > --
    > Michael Jackson | Owner, President
    >      BlueQuartz Software
    > [e] mike.jack...@bluequartz.net
    > [w] www.bluequartz.net 
    > 
    > 
    > 
    > 
    > _______________________________________________
    > Qt-creator mailing list
    > Qt-creator@qt-project.org
    > https://lists.qt-project.org/listinfo/qt-creator
    
    -- 
    Eike Ziller
    Principal Software Engineer
    
    The Qt Company GmbH
    Rudower Chaussee 13
    D-12489 Berlin
    eike.zil...@qt.io
    http://qt.io
    Geschäftsführer: Mika Pälsi,
    Juha Varelius, Mika Harjuaho
    Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
HRB 144331 B
    
    


_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Reply via email to