Some time ago I've moved from mySql's phpMyAdmin to postgres's pgAdmin 4.
What I've noticed is that pgAdmin's query tool has very slow autocompletion. Usually it's just faster to type keyword/identifier on your own than waiting till autocompletion will appear.
When I click ctrl+space it takes around 0.5-1 second to appear, horrible.
In compairsion when I use autocompletion in phpMyAdmin, it appears almost immadiately.
My question is, does it work so slowly for you too? Is there any way to fast it up? Or I have to use some third party program to get faster autocompletion?
Cheers.
[EDIT]
I've also tried the online trial of pgAdmin and here autocompletion is a little bit faster but still not even close to phpMyAdmin's one.
Just to add to this, the autocompletion has made pgadmin unusable for me. If I briefly pause to think about a query while I'm navigating, suddenly a list will appear over the SQL I'm looking at, and the arrow key context will be hijacked to navigate that list instead, which is, as you can imagine, jarring.
Related
When developing my react app the app becomes unusably slow with the devtools open in chrome. Works fast and fine with them closed or in incognito mode. I have tried disabling all extensions and had the same problem. This seems to have started happening recently when I updated chrome (now on Version 80.0.3987.132).
I am not really sure where to start debugging this issue but it has become very frustrating to develop on my app.
Any advice or help debugging would be appreciated.
TL;DR: Go to the Sources tab and delete all breakpoints for the site.
I had a similar problem. My site was very slow to load, but only in specific circumstances:
Dev-tools were open.
Tab was in a normal window. (not incognito mode)
Profiling was not enabled.
If (and only if) all three of those conditions were met, the site would load unbearably slowly (15+ seconds; normally ~3s), plus have performance issues for certain operations on the site (like changing which subpanel was open). It was very strange.
Like you, I tried disabling all of my extensions, yet the problem persisted.
Attempt 1: I tried clearing all of the site's cookies and local-storage, using the info/lock dropdown at the left of the address-bar. Suprisingly, that seems to have fixed it! (edit: this was not the root problem; see below for that)
So the problem must be that my site was storing too much data in local storage or something, such that dev-tools was choking on it (but only in specific cases, for some reason). This also matches with the issue resolving in incognito mode: incognito mode uses a "clear slate" for site cookies/local-storage.
Anyway, it's an odd one, but the cookies/local-storage clearing seems to have worked for my case. (If the issue comes up again, and the solution above doesn't fix it, I'll try to remember to mention it.)
Update: Oddly, having the profiler on still speeds things up even after the fix (ie. those three conditions being met still slows down page loading and actions, just much less than before the fix). So apparently the fix merely "reduces the intensity" of the problem rather than fully fixing it; like, by resetting local-storage, it lessens the size of that data, which somehow is a variable affecting the core problem (not yet identified).
Attempt 2: I believe I have found the root problem and solution: I removed all breakpoints for the site, and the slowdown was solved completely. So the problem seems to be that I had lots of unneeded breakpoints set at various places in my website code (some enabled, some disabled). Some of these must have been placed in/near "hotspots" that were getting called frequently. By having the dev-tools open, the Javascript engine must have had to start performing some processing related to the breakpoints, slowing things down.
My guess is that the problem would also be fixed by disabling the "JavaScript source maps" settings (as that's the only thing I can think would cause so much slowdown), but I haven't confirmed this.
This has most probably something to do with this commit, titled "Stop sending profile data when recording is off".
They already know there is an issue with the Developer Tools slowing down and they tried to prevent it by preventing profiling data to be sent via the bridge to the frontend, when not recording.
As reported, it seems the issue is not happening anymore, on the latest version. However, the cause is still unknown.
Try uninstalling the Developer Tools extension, clearing browser cache and then installing it again.
You should probably try using a version other than the one you're using, Version 80.0.3987.132. The app you are trying to develop might not be suitable to the version you are using. Delete the extension you are using, clear and remove every trace of browser cache and then re-download the extension, like what Daniele Molinari said. It might help. If it doesn't let me know. I'll try a different approach.
Very often, when I open File Explorer (on Windows 10) it "hangs", showing empty panels with a search bar on the top slowly moving to the right, with nothing else happening. However, if I open a second (or third, etc....) instance of the same file explorer, it immmediately works showing all the files (while the first keeps on "searching" with no results). If I close everything and re-open the Explorer, once again the first instance hangs on this sort of search activity, while the second works OK.
Unfortunately this behaviour is a bit random (see the "very often" above). I have tried closing any other program that might interfere, but couldn't find anything. I also couldn't find much help by googling it. My guess is that by using the PC at some point I run some program that corrupts something ...
Any hint on where to look?
I just ran into this problem for the umpteenth time, and I definitely found the fix for this iteration. After trying several things, this was the instantaneous fix for the slow scanning bar and slow column sorting:
Navigate to the problem folder in the Window Explorer folder view.
Right-click the folder and select "Properties".
In Properties, select the "Customize" tab.
Make sure "Optimize this folder for:" is set to "General Items" AND "Also apply this template to all subfolders" is checked.
Click OK.
This immediately brought my problem folders to life and everything worked normally. I would recommend doing this at the Drive level folder, and then go back and customize folder such as Pictures, Music, and Videos. The reference that solved the issue is quite old, but still seems to be an issue (and the fix).
Before this I had tried rebooting several times, cleaning out shortcuts, sfc, dsim, and several other things that did not have any effect. Now opening any folder is lightning fast with no scan and sorting by name, type, size, or date modified is just as quick.
Today I came across a bug that I'd like to share with everyone.
When trying to execute an SSIS package in Visual Studio (2015 and 2017 the following can happen (note this package was executed sucessfully before).
While on the bottom it clearly says the SSIS package is finished, the data flow task is still in progress (and will never finish). What also happens (don't know if consistently) a CMD window pops open with "SQLDUMPER.EXE".
This is not due to the way the steps are configured, since executing them individually might still lead to the proper results.
Note as well that in my case this problem makes Visual Studio incredibly unstable. It is not uncommon that after or during every execution Visual Studio crashes completely and is automatically shut down by Windows.
There are no error messages and I had no idea what the reason is this happened untill... (answer below)
After a lot of googling i've found a reason whya multitude of people seem to have this problem.
Right click the project and then click on properties
Click "Debugging"
Set "Run64BitRunTime" to "True"
Apparently for most people this fixes the problem.
For me however I had to come up with another solution.
Right click the project and click on properties
Click "General"
Set "TargetServerVersion" to either the target SQL server and run the package again OR set it to any SQL server version, run the package to see if it works, and if it doesn't set it to another version.
These solutions are counter intuitive because this problem seems to arrise at a random moment and the target sql server version might have been the same throughout the entire development.
I have not tried to see what happens when I deploy the bugged project to a server and see if it runs there, so any and all extra information on this problem would be appreciated.
I spent a good bit of time googling this problem. It looks like it is being reported by many people around the world. It is usually down to either x32/x64 compatibility or some miniscule issue with sorting or data sizes or compiling a custom C# script (or combination thereof).
None of these things worked for me so I rebuilt the entire package from scratch and the issue was gone.
It is far from perfect, especially if your package is large and/or complex but if nothing else works, this is your last resort.
"Run64BitRunTime" was already set to "True", but I was getting this error. so I restarted the visual studio and problem resolved.
None of the proposed solutions worked for me. I had to rebuild both the solution and the project a couple of times and this fixed it. Of course, I opened and closed the VS a couple of times in between. I guess this is a bug and you have to tinker with it to get it to work.
While exporting a Solution from CRM, I dont get the prompt to save the exported solution.
I cleared Cookies and tried,
Upgraded to IE 9 also and tried,
I made sure that the Popup is not blocked, but these things didn't help.
This is the case with few other colleagues of mine also.\
Thanks
I usually get a popup right at the bottom of the window. Its not instant however, Crm has to generate the solution file, so if its particulary large it can take a minute or two. I would suggest clicking export, finish the dialog and then waiting 5 minutes to see if anything happens (it needs a loading icon really).
If that doesnt work, try the same again with a small solution (one entity).
I know it is too late but I am adding the solution here if someone faces the issue again.
The issue was due to URLScan. It was solved by removing URLScan from ISAPI filters for CRM web site.
Stumped here. Posted a similar question before. We have a pretty large WPF app that on some machines runs great, but on others, all of a sudden, one of the CPU cores gets pinned at 100% (just one core) and the app freezes. It usually seems to happen when showing a context menu or a combobox drop-down (i.e. Popup controls) which is why we can't debug this since no user code is executing at that time. It's driving us crazy because again, on most machines it runs fine, but on a few, it freezes.
The odd thing is when we run it in a VM, it runs great there too! Crazy! Not sure what's causing this, or more importantly, where to even begin to look because as I said, no user code is running.
This happens on only about 10% of our machines, but it consistently happens on those machines. All are clean (i.e. relatively fresh OS installs, no crazy apps, etc.) and mostly identical machines spec-wise: similar CPUs, similar RAM, same video drivers and service packs.
So as I stated in the title, can anyone suggest possible reasons why a WPF app would pin the CPU and lock the app on some computers but not others? We're just stumped!
Found it!! Turns out there's a bug in .NET 4.0 regarding UI Automation and the changes MS introduced. Here's the info, and the fix! (Note: Even if you call MS, they will send you a link, but it's always a broken link. I managed to track this down manually.)
Note: Their article talks about a specific case that causes this behavior, but if you google around, you'll see tons of issues around hangs related to those DLLs. The latest is they're promising a fix in the .NET 4.5 runtime (from a MS post on this issue.)
Here's the KB article...
http://support.microsoft.com/kb/2484841/en-us
...and here is the actual hotfix.
http://archive.msdn.microsoft.com/KB2484841/Release/ProjectReleases.aspx?ReleaseId=5583
Crappy video driver? Pull two machines - one where it happens, one where not, and start analyzing differences. Could be hardware defects, bad video drivers, anything in that area. WPF uses the GPU to render if one is there.
Since you seem quite to lack options, i would advice to make a new project with just most basic ComboBox in the Window, doing almost nothing. This should work (check :-) ). Then you add features one by one in the ComboBox and test, for instance when you add command, start with empty one. Do this until it 'breaks'. So you know which feature is the culprit.
You didn t say if all was working with software rendering.