Note: I'm using an M1 Apple Silicon MacBook
Not sure if this is linked:
So I was using Atom to do some CSS editing last night. When trying to close it, Atom wouldn't close and the computer actually crashed. The file wasn't saved anywhere and was just a throw away copy paste editing file.
Today I started up my computer and opened Google Chrome and everything is busted. I've attached some images, one showing what it looks like in the inspect window, with a giant red box around everything, this has not been added, this is what it looks like in my Chrome > Dev Tools. It seems like the CSS of Chrome has been damaged in some way? I'm not a very experienced programmer.
I tried to reinstall Chrome and delete all Chrome Application Support files but the issue remained.
Also checked the Dev Tools > More Tools > Changes window
Does anyone know how this is happening?
Fixed this with the following:
Deleting chrome from Applications and emptying bin
Did a search for all files with "Google" and deleted 3 remaining files named "Google".
Deleted the Google files found in Application Support
Ran an Avast scan (found nothing)
Did a full cache/history clear
Related
I'm new in StackOverflow and I'm a beginner in web development thank advance for your comprehension.
I have problem with SASS
it tells me well in my terminal that it compiles my code on my main.css but this shows me the result only a few times on my browser (Firefox and I cleaned his caches).
I use the terminal of VSCode (Windows Powershell) I have SASS with node.js and local server with WAMP.
I find it hard to understand my other projects I did not have this problem.
Know what I can do to fix this?
You can find my code on GitHub and a video to show you the problem.
Thank you and have a good day!
Code of my project on GitHub: https://github.com/ValentinBnmr/Semaine_Inter
Video:https://youtu.be/dV_FcwNwwcY
PS: Sorry for my poor English.
First of all, check if the value actually changes within the compiled css file. Since your Sass compiler tells you that it compiled everything successfully, it should then be changed within your css file.
It is most likely your browser's cache. Clearing it once has no effect on later reloads as seen in your video. You can set your browser (both Firefox and Chrome) to deactivate Cache while developer tools are open.
Chrome: open DevTools [Ctrl Shift i], open its settings (either hit [F1] or open via DevTools menu), under "Network" check the box at "Disable cache (while DevTools is open)
Firefox: open Web Developer toolbox [Ctrl Shift i], open its settings (same with Chrome), under "Advanced Settings" check the box at "Disable HTTP Cache (when toolbox is open)"
Whenever you load a site with those tools open (as it should be when doing stuff like this) you will never run into cache issues anymore.
The problem is awkward because everything worked fine. I opened the laptop and somehow it crashed and didn't corresponding to any commands so I had to turn it off. After I started again and after building my project(just in case anything was wrong) and opened my web page I realized that bootstrap is not working at all, and I can't figure out why because I didn't do anything. I tried to install a lower version and didn't worked and after I install the latest stable version and not didn't worked again. If you need any source code let me know and I will edit my post. I will put a picture below which describes what I am talking about(or at least I hope so).
It has the appearance of running in IE Compatibility mode, even though you're on Chrome. Try refreshing your cache (Control+Shift+Delete), rebuilding your project, and using a different browser.
I've run in to this issue before and refreshing the cache usually does the trick.
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'm using watir-webdriver to navigate around my website and grab screenshots in different browsers.
Sometimes the screenshots taken in IE turn out the right size, but colored entirely black. The firefox tests that get run at the same time look fine.
browser.driver.save_screenshot(screenshot_dir)
Once I remote desktop to the computer running the tests the IE screenshots look okay again. A little bit after leaving remote desktop the IE screenshots go black again.
I'm running these tests on a instance of Windows Server running on ec2.
Based on your comment that remotely accessing the machine resolves the problem for a little while... disable the screensaver on that box. I'm not sure how (if at all) the screenshot functions on IE and FF differ, but it's worth the time it would take to test the change.
Edit: I still feel like it's windows/power setting related as you logging into the box appears to have an effect, but I don't know what else specifically that could be. I tried a programmatic approach below vvv.
From what you are saying, it sounds like the Windows system is automatically locking, like it should. This would explain why screenshots work fine when you remote in, and then go to black several minutes later when the screensaver kicks in and locks your system.
If the Windows system is locked, screenshots are blacked out. This is a Windows security feature.
I would be curious to know if FF really does do screen captures on a locked system.
Here's the code I'm using to capture screenshots (Watir-Webdriver, Cucumber). I use remote Windows XP VMs for my test boxes, and have not encountered the issue using Firefox or Internet Explorer.
We did find that when you view the log with the embedded screenshot, it does not seem to work in IE - so you have to use Firefox for viewing. It's base64, so there doesn't seem to be a logical reason for this.
After do |scenario|
if scenario.failed?
encoded_img = #browser.driver.screenshot_as(:base64)
embed("data:image/png;base64,#{encoded_img}", 'image/png')
end #
end
Using Flex Builder 3 :
I have been getting this problem in every single debug launch for past few hours.
I used to get this earlier too, but once in a while, not with every debug launch.
I found out that flex debugger uses a certain 7935 port but I can't figure out
how to change it?
I remember getting this problem a few times. It might have to do with the Flex Profiler (I used to accidentally click that every now and then trying to launch the debugger).
If you start the Profiler and stop it too fast, it will add something to a file in your home directory that it shouldn't.
Check out /path/to/home/mm.cfg on your operating system (on mac, you can open it in textmate with mate ~/mm.cfg). The mm.cfg file stores some information about debugging in Flex
Then in that file, make sure this is the only content:
ErrorReportingEnable=1
TraceOutputFileEnable=1
If there's an extra line (can't remember/find it, something like PreloadSwf=/Users/[username]/Documents/workspace/.metadata/.plugins/com.adobe.flash.profiler/ProfilerAgent.swf?host=localhost&port=9999), delete it.
Let me know if that fixes it.
Lance
Also just make sure you're not using Chrome. Flash Player debugger (at the time of writing this) does not work in Chrome.
This worked for me: right click on a SWF, select "Open with...", choose "Other...", select the Debug player and check the "Always Open With" checkbox.
Mac OSX / FlashBuilder4
Right click your launched flash application, either in the browser or standalone flash player and click on debugger if enabled and change the radio button from localhost to other machine and enter the ip 127.0.0.1 and you are free to debug. I guess the problem maybe from your host file.
Changing the browser from default (chrome) to IE worked for me
Similar to danjp - This started happening to me after a Flash Player automatic update. I simply reinstalled the debug flash players from the Adobe Flash Player download page and everything works as expected.
Make sure there is a swf file with the proper name in your bin-debug directory and that name matches the swf name specified in index.template.html file for the project.
I had replaced index.template.html file by mistake with a similar one from another project. When I tried to debug, I got this "Waiting for flash player to connect to debugger…" status till it timed out.
To me the problem was that internet explorer opened and showed a certification problem, if i didn´t continue this the debugger would show this error. If i continued on ie, no problem happens.