11 Replies
      Latest reply on Dec 3, 2018 1:39 AM by Claude31
      Mic Level 1 Level 1 (0 points)

        This is annoying to a point where Playgrounds are basically useless. Happens to me all the time. Best MBP and all the latest versions.

        Defeats the whole purpose of Playgrounds if it takes minutes to get them running. Have to quit Xcode all the time.

        • Re: Playgrounds get stuck "Running..."
          Claude31 Level 8 Level 8 (5,335 points)

          It may help to set manual execution mode (the square at the bottom).

          • Re: Playgrounds get stuck "Running..."
            loulou64 Level 1 Level 1 (0 points)

            Hi Mic,

            Same issue for me, my Playground get stuck as soon as an error comes in as:

            error: Execution was interrupted, reason: signal SIGABRT.

            The process has been left at the point where it was interrupted, use "thread return -x" to return to the state before expression evaluation.

            Need to quit and relaunch and at relaunch long time with Lauching Simulator...

            Really disappointing.

            • Re: Playgrounds get stuck "Running..."
              Claude31 Level 8 Level 8 (5,335 points)

              Could test 9.4 beta2:

               

               

              Playgrounds

              Addressed an issue that would cause Xcode to hang when using Playgrounds. (37822125)

               

              • Re: Playgrounds get stuck "Running..."
                GRS57 Level 1 Level 1 (0 points)

                Playgrounds working again for me in  Version 9.3.1 (9E501).

                • Re: Playgrounds get stuck "Running..."
                  groupaccount Level 1 Level 1 (0 points)

                  Would have to agree with you Mic - the playground in 9.3.1 hangs on "Running" incesantly and when I installed the 9.4 beta guess what - same thing.  Was excited to use the playground yet it 100% useless and a waste of time.

                  • Re: Playgrounds get stuck "Running..."
                    pkclsoft Level 1 Level 1 (10 points)

                    Yep, with Xcode 9.4 on High Sierra latest versions, I'm trying to prototype some SceneKit code in a macOS playground.  My machine is a MacbookPro Retina (early 2013), 8gb ram.

                     

                    It's so unstable I have to restart Xcode (if it hasn't crashed and restarted itself) at least once an hour.

                     

                    I find that:

                    1. Saving files triggers crashes.

                    2. Editing anything other than the main playground entry code does not cause the playground to recompile automatically or quickly.

                    3. If an error exists in anything other than the main playground entry code, you get this stupid modal dialog on the screen with "The auxiliary source module did not compile successfully." as the message.  Just show me the error messages inline like any other compilation issue, thanks.  And when I have two displays, that dialog insists on showing on the primary display, not the one with Xcode (which I run on the larger, secondary display).

                    4. Code completion both automatic, and via the ESC key does not work in anything other than the main playground entry code.

                    5. I see a lot of these SIGTERM errors after watching the beachball for 30 seconds.

                     

                    "error: Execution was interrupted, reason: signal SIGTERM.

                    The process has been left at the point where it was interrupted, use "thread return -x" to return to the state before expression evaluation."

                     

                    Honestly, the whole "swift" experience is painful.  I can try reworking my playground into a mac app to see if it's more stable.  God forbid kids actually try to learn with this stuff.  It will turn people away.

                     

                    [EDIT]  I've just taken my code out of the playground and copied it into a new macOS.game project.  Same code with the only tweaks being the game view initialisation stuff that had to change slightly.  Now, the thing runs first time, every time.  So I've wasted all this time on Playgrounds which are slower to compile, less intuitive to use, can't be debugged, etc when I could simply be running the app natively and quickly on the mac.