Not a VERY big deal, but it's still annoying. Qt Creator shows Not Responding for a few minutes upon startup, then it's OK. What could be the reason? How to fix it? I have cleared my temp files, also have given Qt Creator admin rights. It still does not help. Below is the screenshot:
Tried disabling the welcome screen as per the suggestion. Now the welcome screen does not show up, but I still have the same problem:
The culprit is likely the "welcome" screen.
Go to help - about plugins and disable welcome.
Another source of delays might be due to an internet connection being unable to go through and waiting to time out.
It is normal if the first time Creator is started to take a little longer while scanning for external tools, but after the initial run it should not be a problem.
As the comment noted, it might be the case of a recently introduced issue, in the case you are running the affectd version - 4.6.1.
For those observing instances of the problem with versions 4.8 and upwards running on Windows 10, I can confirm Windows Defender having a role in it.
Disabling the Welcome Plugin does not always solve the problem, as this is also triggered by first-open of the File menĂ¹ (which populates Recent Files/Projects submenus) or often by simply hitting Ctrl+K.
My solution consisted in adding Qt Creator to the Windows Defender exclusion list.
This is done by navigating Windows Security -> Virus & threat protection -> Virus & threat protection settings -> Exclusions.
Then add a Process exclusion entry using the path to the Qt Creator binary directory, such as C:\Qt\qtcreator-4.9.0\bin\*.
Note the presence of the final \* bit, to whitelist all binaries in that directory.
Related
today we received info from one of our customer about this malware detection:
Gen:Variant.Adware.Kazy.795337
It's only inside the qwebp.dll file attached to our project by qtdeploy process.
We're building 32-bit Qt (5.13.2.0) from the source and the same issue is reported on the same DLL no matter where it was built. We're using the latest VS 2019.
https://www.virustotal.com/gui/file/9f09c05803ad4ffcd99454c420a840e17549ee711690fb1f11fd1b59bccc3b23/detection
https://www.virustotal.com/gui/file/80c4c747d781a27c72de71c0900ccc045aefd2b4e4f17c949aaeeb3d0b7973b1/detection
When I scanned the older version (5.13.0.0) everything is ok:
Previous versions seem to be clean:
https://www.virustotal.com/gui/file/b7b7cacaef0e76439ef8c367c401524e93dfa00c9ca67a20290e829fec325a5a/detection
Also, any debug build and 64-bit builds are clean too.
Any idea what can cause this? Can anyone else please try to scan this file?
Thanks
TL;DR: It is probably nothing, but notify Qt anyway (and check your own systems).
Are you using the prebuilt Qt binaries or are you compiling the sources yourself?
If you are using the official prebuilt binaries, I'd of course expect that the Qt Devteam scans them and verifies that they don't accidently spread malware, but there is always the miniscule chance of something slipping through.
Same goes for the sources - while their review process should be thorough enough to avoid malicious code being slipped in, there is still the outside chance of either a key account being compromised or (even more unlikely) bad code being added slice-by-slice over a longer time period to avoid detection (along the lines of the underhanded C contest). Still, either case seems to be rather unlikely.
Bottom line: while this does sound like (and probably is) a false positive, you still may want to raise an issue with Qt e.g. on the their Bugtracking site or directly with Qt support (if you have a commercial license) to be sure. Also (if you didn't do that already) verify that the problem is not on your end, e.g. that your computers are clean and that you don't just randomly catch/detect your infection in that file.
Update:
A ticket concerning this issue was opened (I assume by Ludek Vodicka) on Qt bugtracker. Opened on Nov 19th and categorized as P1: Critical, but unfortunately no indication that it is actually being worked on (at least of Dec 18th).
After I open Goland and leave a project open for a while, like 10 minutes and sometimes less, Goland just closes down without any notice. I thought it could be related to the settings, especially to those related to memory as shown here:
Xms128m
-Xmx750m
-XX:ReservedCodeCacheSize=240m
-XX:+UseConcMarkSweepGC
-XX:SoftRefLRUPolicyMSPerMB=50
-ea
-Dsun.io.useCanonCaches=false
-Djava.net.preferIPv4Stack=true
-Djdk.http.auth.tunneling.disabledSchemes=""
-XX:+HeapDumpOnOutOfMemoryError
-XX:-OmitStackTraceInFastThrow
Is there any setting I can change to stop this sudden closing?
I am on Windows 10, build 17134
Please ask your question on our official support tracker, and provide the IDE logs via "Help | Compress Logs and Show in...". If the zip is too large to upload then please use the upload service and specify the file name in the ticket.
I cannot provide any further help here due to the nature of the issue, sorry.
I'm currently on my third attempt trying to install Visual Studio 2015 on this computer. I have tried rebooting, hard shut downs, canceling setup and restarting, etc. Each time, it gets stuck at applying Microsoft ASP.net. I have tried leaving it overnight (12 hours). My download speed is 50-60 MBPS according to Ookla Speedtest. I am running Windows 10. I did do a "custom" installation and added C++, Python, and the Git extension. If I am not mistaken it said 7 GB size. Why is it doing this? Please help!
I don't understand why this isn't working because I installed VS 2015 for my laptop (a different computer) just a few days ago on a relatives WIFI and their speed was 3-7 MBPS.
(Note: The installer is not technically frozen since the loading dots on the bottom are moving.) However, bar hasn't filled up at all for like 6 hours.
EDIT:
Do I need ASP.NET (for C#, Python, and maybe C++)? Can I uncheck certain features for installation so that it wont try to install this? Also, when I cancel installation it never cancels and just stays there so I have to kill the installer with the task manager. This is getting incredibly frustrating.
Fixed it...
Easiest way is "threaten" to shut down the computer. Go into Power, restart system. You will be warned that there is a logging program which will not let the system reset. Cancel that program and then do NOT restart.
Installer immediately went on to next part and finished install after having been stuck for 6 hours...
I got it to work, it wasn't perfect, but here is what I did: It was getting stuck at very certain points, most notably ASP.NET. I did a little research and got an idea from something I read (I unfourtunetly can't find the source again). Sometimes windows opens invisible "confirm" type windows or installer windows that get stuck. When the installer got stuck I opened up task manager -> details, than checked On the visual studio process by right clicking then clicking analyzing wait chain. This showed me what process the VS install was waiting for. Then, I'd just kill the process. Messy, I know, but better then nothing. I had to do that 2 or 3 times. Afterward it said it installed correctly with 2 components that had warnings. ASP.NET was included. But everything else worked fine (c#, C++) Later I went back and did a repair. That worked pretty smooth. Finally, I installed the Python Tools successfully. (that part is sort of irrelevant but the point was that everything is now working fine).
edit, found another source: Visual Studio 2015 Community Edition Installation Stuck In Windows 10
Yes i had this problem too. To solve this open task manager and go to details tab then search for TiWorker.exe, right click on it and choose analyzing wait chain it will display many instances of the process that are in waiting mode , check all those processes and terminate them after doing this the installer will go to the next step.
To avoid this problem, you have to install IIS first.
Go to Control Panel -> Programs -> Turn Windows features on or off -> Select "Internet Information Services" -> OK
I had this problem a couple of hours before writing this answer and what worked for me was:
I opened other programs at least two or three and went to power and clicked on restart as usual it will warn you about open programs that need too be closed before shutdown or programs that are currently active I then clicked on force close and it closed the first program that I recently opened then I quickly clicked on cancel. Two minutes later instalation was back on track
Press Ctrl+Shift+Esc, then go to Tiworker.exe and terminate all the waiting processes.
I found a solution to this headache of a process to install Visual Studio. If you have tried everything and nothing seams to be working for you even by trying the command line shell then try this.
Go open task manager while running the installer and kill wusa.exe. It will kill the process to search for the update and continue the installation. You may have to kill some other processes as well if they get stuck. Its not great but it seams to be working.
wusa.exe seams to be the task that is the problem that prevents the installer from moving to the next step. This could be because your computer can not reach the update server.
This seams to be the case for both the Community and Enterprise Version of Visual Studio.
I am using VS2010 on Windows XP pro (sp3, x86), and I just installed the hotfix kb2106584. This fix was reported by some people, example here, as having a fix for an issue I had with Asp.Net Development Server not getting opened properly from VS, which I was having previously. My issue was being caused by ESET NOD32 messing with the http traffic from devenv.exe and causing all the ports in my computer to get used up, however.
Anyway, as soon as that was finished, I opened my website back up, and clicked debug. Asp.Net Dev server pops up, which was what the hotfix was supposed to make happen, and then notepad++ opens with the tabs I had last time I used it, and IE never shows up. "Wait, what?" try it again. and again. Always notepad++, never IE, always with no new documents opened, just some completely unrelated stuff.
I've seen one other post on SO about this happening, here, but his issue was corrupted files/filesystem. My project is in source control, so I tried a delete&revert to yesterday's revision. Still opens notepad++, so that's not my issue.
I've also tried rebuilding, which did nothing, and deleting my local Solution files, which also did nothing. I restarted the program and then the computer, both to no avail.
I start to believe that this is the hotfix screwing things up, so I try to do a system restore to a couple days ago. Once again, no dice; it's still pulling up notepad++ instead of IE.
So, the questions become:
Is there a setting or two I can try changing to make it open the proper program again?
Or was this a bad/improper hotfix, and if so, how do I uninstall it? It doesn't show up in the Add/Remove Programs dialog, and I don't see an option to uninstall it in VS, or in the installer.
Thanks in advance.
[edit] Also note: Notepad++ is not actually opening the website file, it's just getting opened with whatever I left in it last time. I dunno if this helps at all, but I felt like details would be appreciated. [/edit]
Fixed:
Uninstalling n++, deleting EVERY registry entry & folder containing 'notepad++' (except one, from whose string I removed ";notepad++.exe"), then reinstalling n++ made VS stop opening notepad++.
Now it opens the default web-browser again.
[edit]
Note for anyone else out there who ends up with this specific and bizarre problem:
It would be worth a shot to try changing the "Browse With..." setting in VS, by r-clicking on Default.aspx to "Internet Explorer". My list included Notepad++ as an available internet browser.
This might be a better solution than the previous, if it does in fact work.
I didn't know this setting would allow Notepad++ as an option until I had to set it back to IE again after all this, and that may have been the problem all along. Apparently, VS just changes this setting sometimes. How or why N++ got put in as an internet browser is completely beyond me, but I did myself the favor of 'Remove'ing NotePad++ from the list, and you may wish to do the same.
Again, I'll never truly know whether or not I nuked everything when I could have changed a single setting that got mysteriously reset, but may this [lesson?] at least be recorded for posterity.
[/edit]
It took all of that to figure out that it [was?] a bogus registry entry somewhere that [may have been?] modified by the hotfix; a registry entry that neither notepad++ nor visual studio 2010 ultimate would clean up on uninstall or replace on reinstall
Which was it? I have no idea. Like I said, I didn't even use n++ this week until VS started opening it for me, and the only change I made was to install that hotfix.
I have a problem with Visual Studio 2010. When I start debugging it works slowly.
Internet Explorer opens, but the website loads extremely slowly.
My workmate and me work on the same project and he doesn't have any problem like that.
My hardware is 4G memory + Intel Core i5 CPU 3.20 GHz.
I stopped my anti-virus program but it couldn't be resolved.
I've had the same problem for over a year! And I solved it :)
I took me about 20 seconds to start debugging, and about 1 minute to stop it. It also took 2 minutes to load the solution! My colleague had NO problems with the same solution.
I found my way out of it by a coincidence.
I CHANGED the NAME of the solution, and things suddenly happened 30 times faster.
I CHANGED the solution name back and it slowed down again!
This is probably a FUBAR error made by the Microsoft development team. Don't try to figure out why it happens :)
This might be a IPV6 issue (that shows itself in windows vista/7 when using firefox or IE). I've had that at work and this is what made pages load instantly when using localhost (instead of the 20+ seconds that could happen on image-heavy websites I was developing).
IPv6 (taken from Firefox cannot load websites but other programs can )
Firefox supports IPv6 by default, which may cause connection problems on certain systems. To disable IPv6 in Firefox:
In the Location bar, type about:config and press Enter.
The about:config "This might void your warranty!" warning page may appear. Click I'll be careful, I promise!, to continue to the about:config page.
In the Filter field, type network.dns.disableIPv6.
In the list of preferences, double-click network.dns.disableIPv6 to set its value to true.
For Internet Explorer, try using http://127.0.0.1:PORT_NUMBER/ where PORT_NUMBER is the port you can see in your address bar. If the loading of the page is faster, then you might want to go check the C:\Windows\System32\drivers\etc\HOSTS file and make sure the only line mentioning localhost looks like 127.0.0.1 localhost.
Check to see if you have _NT_SYMBOL_PATH environment variable set. Getting symbols or pdb files for the assemblies used by your application from a symbol server could be the cause of the slow startup of your application when debugging. You can also look at the symbols setting in VS>Tools>Options>Debugging. Also, take a look at the output window and the status bar down at the bottom in VS when your app is loading and taking a long time to see what VS is busy doing.
Not sure if this applies to ASP.NET applications, but disabling the 'Show Parameter Values' option in the Call Stack window's context menu considerably speeds up the debugger on my machine.
Two things to check.
1. Remove all the parameters in the watch list.
2. Build >> Config Manager , Check the Configuration Mode: Debug/Release.
I have encountered the same problem. I could make it better by deleting the Folder created in the temporary aspnet folder. For that you need to close the solution that you have opened and then delete. I don't know if there is any other solution.