I upgraded to vscode version 1.75.1 (user setup) yesterday. Today, while debugging, I noticed something very strange. The variable I am watching in the debug window seems to display the wrong values sporadically. I can step through simple console.log statements and watch the variable change values. See the sequence of images. You will a large object in the watch window and logged to the console screen. The next image is one tick away, and while the correct value appears in the console again, the watch value is a completely different value. In the third image the correct value is displayed in both locations. This is not an issue of concurrent execution. Is anybody else seeing this?
Version: 1.75.1 (user setup)
Commit: 441438abd1ac652551dbe4d408dfcec8a499b8bf
Date: 2023-02-08T21:32:34.589Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: 10.2.154.23-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No
Rebooted and still have the same issue. Will try reverting vscode next.
Here is another example. No way to get into the if(cost.error) statement at the bottom if the value in the watch window (cost.error == undefined) was correct.
Switching back to version 1.74.3 does NOT have the same issue
Looks like a bug that has now been identified: https://github.com/microsoft/vscode-js-debug/issues/1561
Related
I'm not really a coder but I use VS Code at work for various reasons on my mac.
If I move between VS Code and my browser, every time I open VS code it freezes for a moment. It freezes if I change tab or move file. Looking at my commit changes or doing anything with the in-built terminal doesn't cause it to freeze.
All the dependency packages are up to date. I've disabled all of the plugins and it still happens. VS Code is at the latest version, 1.67.0.
I really don't know what is causing it and would appreciate any help!
what I did is just changed the color theme and after that, it is stopped working as expected regular behavior, It is not showing suggestions, VS Code IntelliCode also not working as before I have done efforts of my side as like uninstalled all extensions and installed them again, deleted VS Code from applications and installed it again. Image You can see the extensions which are using currently and also you can observe that I'm using the style of justify-content when I typed the quotes then it is supposed to show all the values available for it. but it is not showing currently
Please let me know, are there any possible ways to get back to the normal behavior of VS Code for Mac?
I already uninstalled all the extensions and installed them again, removed VS Code from Applications. and downloaded the latest version from the official VS Code site.
Folks, this is not a code question but I dont know where else to post this. the website of VS Code linked me here so here goes.
Here are my visual studio code version details
Version: 1.26.1
Commit: 493869ee8e8a846b0855873886fc79d480d342de
Date: 2018-08-16T18:38:57.434Z
Electron: 2.0.5
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
Once I updated to this version, the entire app started looking blurry. It was fine before the update and has been looking fine on this windows 10 machine.
I got other Microsoft Apps - Office Word, Excel and the rest, and they all fine. Visual Studio (regular) looks fine. Its this software and only since the latest update to 1.26.1
Note: There is one other software which always had a blurry appearance, and that is Postman. I assumed that it is a Postman issue so never got around to fixing it or try fixing. adding this here if there is a connection but the question is primarily about Code, and how I could fix the appearance problem.
Update 1 :
So, I opened Postman and that also has stopped being blurry. So, looks like the blame does fall on AMD Radeon rather than MS or Postman developers.
NVIDIA Control Panel
Manage 3D settings
Program Settings
Select VS Code from dropdown or add it if it's not there
Set "Antialiasing - FXAA" to OFF
https://www.reddit.com/r/vscode/comments/9szgkp/visual_studio_code_blurry/
I know this is late but just in case it didn't work for someone, here is another solution:
Right click on VsCode and go to properties.
Copy this command
--disable-gpu --enable-use-zoom-for-dsf
and append it to the target path n the shortcut properties dialog.
Click apply and the reopen VScode.
Here is the article that I am referencing https://medium.com/kasun-kodagoda/fix-text-becomes-blurry-when-vs-code-application-loses-focus-issue-on-windows-d95697b2f927
Try turning Off Anti-Aliasing in your Graphics Settings.Since it Over Renders the Text.
Go into your settings and type "rendering" you should see "Terminal > Integrated: Gpu Acceleration" if you turn if off it should fix the problem.
Go to settings.json and add - "terminal.integrated.gpuAcceleration": "off"
I have a problem every now and then where just the terminal gets blurry. I simply zoom in and zoom out ("⌘=", "⌘-") and it fixes them problem.
For AMD:
Open AMD Radeon Software Panel
Go to Settings > Graphics Tab > Advance Settings > Morphological Anti-Aliasing (x) disable this option.
IMAGE LINK
First of all please accept my apologize for not responding so soon, I
am afraid I can't provide you with a feedback because the issue were
my AMD Radeon Graphics Drivers, after an Update was released the issue
was gone. Thanks for your hard work!
Read this comment on github.
It is possible that there is some kind of an issue with your Graphic card, try updating your Graphic card drivers.
I tried updating my drivers as suggested by Yashu Mittal without any luck. After some tinkering I realized that it is because I had set Anti-Aliasing to something other than "application control" in my graphics card settings.
For those who have a similar issue but in Visual Studio IDE (currently, I am using 2019 edition).
Go to "Tools -> Options -> General", and turn on "Optimize rendering for screens with different pixel densities"
link to the settings image
Bounty Update
I am leaving the question essentially the same, but I just want to point out at the beginning here that I'm most interested in help trying to get the socket between flash (Adobe Animate) and the native debugger working again, as I believe that is the issue I'm having. Or is it a socket between flash and Windows?
Original Question
I've apparently turned something off? Even when I write really bad code (like trying to call a function that isn't there or divide an integer into a fraction), the flash player boots, shows a background color and stops there. No messages in the output window or compiler errors window. If I fix my code, it all runs fine, but for about 30 minutes (ever since I started trying to work with bitmaps for a sprite sheet) I get no runtime errors no matter what kind of mistake I type in my code. Anyone know how to turn it back on?
I've checked my actionscript settings and I have both warning mode and strict mode checked on.
Could it be a socket issue? I admit I have little to no experience working with sockets and only a surface understanding of what that even means. I've added the socket tag. If someone can see that this is clearly nothing to do with sockets, by all means, I'll remove the tag.
UPDATE: 6/22/16
I just reinstalled Adobe Animate CC 2015.2 and no change. I'll try compiling it in flash builder when I get a chance to help pigeon hole the problem. (Edit 6/24: flash builder worked! But my trial version expired the next day so is no longer a viable option).
And I just tried something in the command prompt in Windows 10 as an administrator:
netsh winsock reset catalog
netsh int ip reset reset.log hit
which I found another user on flashdevelop.org used to fix a similar issue, but no change.
And I just tried debugging in Flash Builder. It worked fine (debugger caught bugs) but my trial version expired the next day.
update 6/24
I've tried launching debugger for AIR from within the Adobe Animate CC IDE and it works fine if there are no bugs; it fails to do anything visible (no Iphone emulator, no swf window) if I put a typo or error in the code.
I also just deleted winsock and winsock2, rebooted Windows, then reinstalled winsock and winsock2. No change.
update 6/25
Just tried a system restore in Windows to set all my files and settings and drivers etc. to the way it was a week and a half ago... Also completely uninstalled all Adobe products and reinstalled. No change. I can only imagine that wiping my hard drive and reinstalling Windows would do the trick, but come on, it hasn't come to that has it?
As VC.One suggested, I checked the compile error window (cannot believe I didn't check before! Maybe when I checked before there were no compile errors... Only runtime errors?) and the errors are showing up there. Does this mean that it's catching compile errors but just not runtime errors?
When you force/test a runtime error... make sure you check
Compiler Errors (ALT+F2) and also Output (F2). By Output I mean the window that shows traces (and runtime issues). One of those two should have some feedback for you.
A possible solution is to save a new Workspace. So with those windows for Compiler Errors and Output both open (or tabbed, I tab them next to my Timeline) go to Window (in top options like File/Edit/Debug etc) and choose Workspace, then into that you choose New Workspace. Give it a name in the pop-up and okay everything.
Flash should always load that current workspace (next time, go to Workspace option again, check that your specified workspace [by name] has a tick next to it...).
Possible pitfalls:
1 - Use the debug player
2 - Make sure there isn't somewhere a try/catch enclosing the portion of code that triggers the event that may lead to an error
3 - Socket issue: may be exported in debug mode but swf cannot connect to debugger (it waits in a blank state for 60 seconds I guess)
4 - Does it compile ok? If there are compilation errors you may get an SWF anyway but then it will not start
...
I'm running MATLAB (R2013b) on Ubuntu (results of ver command are pasted below).
I've just started working with this system, and I've realized that coding is seriously hard because the typical "tooltips" that show up in the editor are empty. Unfortunately I cannot paste screenshots, but here I describe the problem: the orange marks on the right margin of the editor should indicate a warning. Passing the cursor on them, one typically gets a tooltip with a short message, detailing the reason of the warning.
In my case, I still see the tooltip... but cannot read anything in there, it's just a gray rectangle. This is terribly annoying... Some idea on what may be the problem?
>> ver
MATLAB Version: 8.2.0.701 (R2013b)
Operating System: Linux 3.5.0-41-generic #64~precise1-Ubuntu SMP Thu Sep 12 16:50:04 UTC 2013 x86_64
Java Version: Java 1.7.0_11-b21 with Oracle Corporation Java HotSpot™ 64-Bit Server VM mixed mode
Are you using the Unity desktop (if you don't know, you probably are, since Unity is the default).
I've encountered your problem with multiple Matlab versions under Linux, and it always boiled down to using a "3D / fancy pants" window manager.
Try using the "Gnome Classic (no effects)", "Ubuntu 2D" or mate sessions and report back whether your problem still exists. Here's a screenshot of the standard desktop login screen in Ubuntu 12.04:
To see the available sessions, do a left-mouse click on the ubuntu logo next to the username (here test):
I had the same problem and solved it without disabling Unity.
Solution:
-open matlab
-go to Preferences->colors
-uncheck "use system colors" for desktop tool colors
-Apply
Now you should see text.
It seems likely that the problem is due to one of 3 scenarios:
1) The relevant default colors in Unity are grey text ion grey background.
2) Matlab Doesn't manage to read the default relevant colors from Unity
3) there is a bug in matlab where it not just greys out the color controls in the GUI but actually greys out the underlying colors.