For faster use add a bookmark, pick a name and paste the following code to the URL:
Go to chrome://flags/#enable-scroll-anchoring the highlighted option is Scroll Anchoring disable it.
Now you will see the message "Your changes will take effect the next time you relaunch Google Chrome." in the bottom with a button RELAUNCH NOW, When you hit this button chrome will relaunch. So first save all your work and then hit this button.
General Tools and settings:
use Chrome + built in Dev Tools + Lightning Component Inspector
be sure debug mode is enabled in your org (Setup: Lightning Components)
be sure caching is disabled in your org (Setup: Session Settings -> uncheck "Enable secure and persistent browser caching to improve performance"
Techniques for most common use cases (be sure ...
Below are the steps for resolution Salesforce provided
1. login and open Developer Console by Chrome
2. open Developer tools and select Network
3. reload on Developer Console
Use the following query to get the IDEWorkspace
/services/data/v31.0/tooling/query/?q=SELECT id, name from IDEWorkspace
and you would get Id: 1de1a0000014sEWAAY
EDIT: This is fixed. It should be safe to dive back in.
Chrome changed the way it accepted inputs to resize methods in v25, so we had to modify our resize code. They're not as forthcoming with release notes and regression testing as we are!
EDIT: This is officially logged as a known issue - Developer Console log viewer fails to display correctly on ...
I have a quick and dirty solution :()
First open a console and query some records. Then open a FireBug window (F12, i hope you have it). Select the query results table with a firebug's select arrow. You need to turn off the css styles -moz-user-select: none for the <div id="gridview-1182" to be able to select the result text. Then select all results just ...
Copy the Deployment ID in your clipboard, and head to:
Click on the Delete button to delete the deployment record, and everything should be back to normal.
You can get it in a pinch using the Code Coverage dropdown from an open class:
If he's hiding... just takes a few steps after launching Developer Console:
File > Open > Apex Class and select one with @isTest annotation
hit Run Test on the top right
go to the Tests tab, expand your test class and double click on your test run item:
this exposes the ...
Try to cancel the save, refresh the console, or both. To cancel the save, right click on the tab and click "Cancel Save". You can also click on the "Progress" tab on the bottom and click "Cancel All Deployments". The Progress tab gives you information on the status of the deploy, but if you are getting that error, it is probably because the save is never ...
Apex uses more resources than a simple API call, such as extra memory, CPU time, etc, so there's additional limits in place. The Developer Console, contrariwise, uses the API, which is just a server-side database cursor. As such, you can technically query up to 50,000,000 rows in the Developer Console (though very large queries may time out or freeze your ...
Sounds like they added something to the Dev console to truncate long lines in spring 19 (On March 20, 2019 according to the Release Note changes).
Developer Console: String Values in Debug Logs Are Truncated
To help prevent connection pool timeouts caused by exceptionally large queries, strings are now truncated at 512 characters in the Developer Console’...
Salesforce is trying to push the use of the developer console. You can still view the color coded view of your classes to see which lines are covered or not in the developer console.
I also find this highly annoying as the old way was much more useful, but SF is really trying to push the developer console.
After running your tests, you need to select ...
As an alternative, you can click on the Progress panel in the developer console and click "Cancel All Deployments."
What is going on?
Apex and VF are interesting because they need to be compiled to ensure the saved state of the org is valid. Before, the only way to do this was a deploy in the Metadata API, which requires a ZIP file and a lot more time.
To use the Developer Console at all, you need the View All Data permission.
To run queries, you need to have the API Enabled permission.
To modify classes and triggers or run anonymous code, you need to have Modify All Data, Author Apex, and View Setup and Configuration.
To change Visualforce pages, components, Lightning, etc, you need the Customize ...
There is a Known Issue for this - Developer Console jumping when using mouse scroll
When working in any piece of code in the Developer Console (apex class, lightning component, trigger and so on) if the user start scrolling down through the content of the piece of code using a mouse wheel, the screen starts scrolling, but then the view ...
The short term solution is to keep playing whack-a-mole~ApexLog as Adrian has suggested.
Longer term, the problem comes back to the Summer'18 update Store Larger Debug Logs with Changed Log Limits:
We increased the size limit for debug logs from 2 MB per log to 5 MB. You can store up to 250 MB of debug logs at a time. System logs are now deleted ...
Other Tools. Your tools list is a good one, as is your question! In addition I would recommend you take a look at the Viewstate contents via the 'Show Viewstate in Developer Mode' setting on your user. This enables the following view on your page. Note that you can use 'transient' to control this for information you define in your controller that is ...
It sounds like you've ran into your API Limit for the 24-period.
Check this. Go to Setup and then click System Overview
You API Usage will be on the top right. If you are at your maximum, I suggest calling Salesforce-Support immediately, and ask to get your API Limits increased temporarily. SF-Support is generally friendly and will usually grant the ...
To set up perspective you need to load some log first:
Then click on the "Perspective All" button and then navigate to "View Panels". Turn some off and save new perspective as "New one".
By the way you can use for example Force.com IDE too:
The Developer Console is using the REST version of the Tooling API to perform the execute anonymous call. The length issue is a restriction of how the call encodes the apex into the URL.
/executeAnonymous/?anonymousBody= <url encoded body>
It is URL encoding your Apex onto the query string. Clearly there are limits to how long this can be.
I found a ...
SELECT Site__c, Cluster__c, Date__c, Num_Att_records__c
Where Session__c.SiteProgram__r.Name = 'Brattleboro' AND Date__c = 2012-11-06
Note the leading 0 on the 06.
The format is YYYY-MM-DD, so you need to pad the extra 0.
Everytime my Dev Console hangs while loading I do the following:
copy the url from the Dev Console window
open new tab in browser's main window
paste URL there
Hope that works also for you.
Sometimes, this is not enough. The console is loaded but unresponsive due to fact that last opened tab is log that is outdated (older than 24hrs and removed).
Did you check "Deleted and archived records:" as "Include" ?
And as for Developer console, you have no way to realize it.
You can realize with Apex using SOQL with "ALL ROWS" option, but Query Editor on Developer console doesn't support it.
After many wasted hours, I found an unexplainable ritualistic solution.
It was mentioned as a small comment on another question.
The ritual is as follows:
Cancel the endless 'saving' operation in the developer console. There's a context menu option to do this when you right click the title of the code editor tab.
Delete the container by the Id mentioned ...
The best current official source for information on the future of the Developer Console would be Nathan Totten (@ntotten).
The last official thing I saw was in The Future of Salesforce IDEs blog post.
I don’t have a roadmap to share today, but I do want to assure you that this is an area we care deeply about and are investing in.
DISCLAIMER / SAFE HARBOR ...