You need to sign in to do that
Don't have an account?
Morgan Marchese
why is developer console so terrible?
Developer console is Salesforce's way for us to check debug logs, track governor limit issues, run queries, and generally just debug all of our developer stuff.... and yet, it's TERRIBLE.
It freezes constantly, it often says it couldn't finish "long running operations", switching perspectives causes the whole browser to lock up, and then once the perspective finally changes it takes a huge amount of time to go from tab to tab (if you can go at all). Once it freezes/crashes, good luck getting it back up because it takes forever to load (if it even loads at all).
This thing is supposed to be our lifeline, our tool to help figure out what's wrong, and I can't even get it to work. Is there an alternative to this poorly implemented program? I can't stand this anymore, I've been trying to suffer through it for 3-4 years now and enough is enough. Why do more people not complain about this tool, and why has Salesforce not released something better by now?
It freezes constantly, it often says it couldn't finish "long running operations", switching perspectives causes the whole browser to lock up, and then once the perspective finally changes it takes a huge amount of time to go from tab to tab (if you can go at all). Once it freezes/crashes, good luck getting it back up because it takes forever to load (if it even loads at all).
This thing is supposed to be our lifeline, our tool to help figure out what's wrong, and I can't even get it to work. Is there an alternative to this poorly implemented program? I can't stand this anymore, I've been trying to suffer through it for 3-4 years now and enough is enough. Why do more people not complain about this tool, and why has Salesforce not released something better by now?
And I am also facing the same issue. And it is banging on as multiple developers are working simultaneously.
This can happen because of these points.
1. Multiple developers working on the developer console at the same time.
2. IF some developers are working on the Lightning component in the developer console.
3. Another, somewhere API is using in org then it slows down the developer console.
Thanks
I appreciate the insight, and I am aware that certain high-volume activities cause more issues in Developer Console than others. The point still remains, Developer Console is a poor alternative to a robust debugging solution, and it shouldn't be subject to so many issues if its meant to be the main source of debugging provided on the Salesforce platform.
Yes, For debugging purpose it's very slow doesn't matter the users. If you want to debug anything you can use debug log. Maybe you know about it. but see below steps.
Setup > Quick Find > Debug Log > Set debug for a particular user and you can see there it will display all the logs very clear.