• Nick Snyder
  • NEWBIE
  • 15 Points
  • Member since 2016
  • Salesforce Software Engineer

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 0
    Questions
  • 2
    Replies
Hello!

I have noticed recently (in the past week or so) that save times on Apex classes using the tooling API have been extremely slow (talking about usually it's max of 10 seconds, now it's anywhere from 30 seconds to 8 minutes). I usually use IntelliJ and IlluminatedCloud, but also tested using Eclipse and the Force.com IDE and experienced the same slow save times.

I did some investigation with other co-workers and it appears to be only on OS X 10.11.6 with the latest 2016-001 El Capitan security update installed. I tested on a machine without that update, to the same org, and the save times were 10 seconds. On my machine, with the update, it was 35 seconds. Co-workers using a windows machine also had ~10 second save times to the same org.

Is anyone else experiencing this slowness? The pod our Trialforce orgs have been spinning up on is NA35. I haven't seen any reports on trust or anywhere else around.

Thanks!
Matt Simonis
I noticed that my Lightning Out App in classic SF is no longer working and the console shows a parsing error.
myVF:504 Uncaught SyntaxError: Unexpected token u in JSON at position 14660



I tried reverting to a version that worked from 3 weeks ago, but it seems to still not work..
Here is my VF code.
myVF.page
<apex:page sidebar="false">
<apex:includeLightning />
    <div id="myDivId">
    </div>
    
    <script>
        var myUserContext = "{!$User.UITheme}";
        $Lightning.use("c:LEXComp", function() {
        $Lightning.createComponent(
            "c:LEXContainer",
            {},
            "myDivId",
            function(cmp) {
                console.log('component created');
                console.log(cmp);
            });
        });
     </script>
</apex:page>

The lightning component works fine separately and within the LEX environment, this seems to only be an issue with Lightning Out.