Ubuntu 20.04 - After suspense problem in chrome browser tabs, The tabs displayed with strange dots(like sand).It happens as well in visual studio code.
Go to the Chrome main menu (3 dots on the top right corner) → More Tools → Task Manager.
Sort by process Task name.
Find the process called GPU Process.
Click on End process.
Related
I currently have a java project which instantiates various browsers via selenium hub/node on various windows operating systems. Is there much involved to expand this to cater for running up a browser on a stock chromebook chromeOS?
The following are steps I tried back in November 2014. The result was unsuccessful and I opened a question on the Google forum with no response.
followed manufacturer's instructions to put the Chromebook in Developer Mode
set chromeos-firrmwareupdate to dev mode and removed rootfs verification from partitions 2 and 4
downloaded and installed Java (latest jre), required for Jenkins slave and Selenium
downloaded Jenkins slave.jar and selenium-server-standalone.jar (2.41.0)
put Jenkins and Selenium in /home and remounted to remove noexec
remounted tmp to resize to 2G (req for Jenkins)
added DISPLAY=:0.0 to ui.conf to set display
added chain rule to allow tcp input
added 'no-sandbox' and 'disable-setuid-sandbox' switches and excluded 'test-type' switch
Result: ChromeDriver started up, opened up a gray screen (a broken instance of Chrome), and closed with an "unable to open pages" error. Weird thing, though, was that the same command used to launch Chrome worked when run from the terminal.
After the recent update, Mac os Sierra, to my Macbook pro, I'm facing scrolling issues with all Java applications like Intellij IDEA community edition.
The scrolling in the editor panes are extremely fast. The unit of
scroll increments seem to be large.
Intellij IDEA Version is 2016.2.3.
Java version is Java 8 Update 10.1.
I see the same behavior even in the "System Preference" -> "Java" -> "Advanced" tab .
This is a known bug, likely caused by the JDK:
It looks like JDK issue and is reproducible with a simple scrollable JList.
Sierra generates much more events than El Captain.
These events contain values ~0.1 instead of expected ~1.
But Java converts these small number to 1 anyway.
Edit: see also this OpenJDK bug: https://bugs.openjdk.java.net/browse/JDK-8166591
Edit2: as described in the other answer, JetBrains have fixed their custom JDK. You can download it here and follow these instructions to make IntelliJ use this JDK instead (select the option labeled ... to choose a custom location).
You need to install JDK from JetBrains as it includes fix for this issue.
Link to JDK:
Unpack it somewhere, press Command ⌘ + Shift + A, paste "Switch IDE Boot JDK" and point to unpacked directory.
Link to instructions from JetBrains.
UPD: JetBrains fixed this issue in latest build. See link.
I am running Chrome Version 52.0.2743.116 (64-bit) on OS X 10.11.3 and upon trying to debug a website realized that the Resources tab in my Developer Tools is just completely gone. What gives / has anyone else noticed this?
"The Resources panel has been renamed to the Application panel. All of the features from the Resources panel are still available in the Application panel."
from https://developers.google.com/web/tools/chrome-devtools/iterate/manage-data/?hl=en
I'm building a mobile application with Visual Studio 2013, using Ripple Emulator and Cordova.
Every time that I try to inspect an element (hitting Ctrl + Shift + I, F12 or right clicking the page and selecting Inspect element) the Google Chrome closes and Visual Studio stops running the application.
Has anyone know why I'm unable to inspect elements inside the browser using Ripple Emulator?
Ps: Visual Studio 2013 has his own DOM Explorer but the experience is not the same as the Chrome Developer Tools.
A simple workaround is to start your project without debugging (Ctrl+F5) from Visual Studio. This will allow you to use the Chrome dev tools (F12 and so on) without killing the VS debugger process and therefore stopping your Ripple session.
I've been having the same issue since upgrading to cordova tools update 3 with visual studio 2015 community edition - it was working fine before "upgrading"
I haven't found a reason why, but there is a workaround which is to start your debugging session (F5.. or whatever) then hop back to visual studio, then select "Detach All" from the debug menu. This, or use a different browser (Edge works fine in Windows 10, but I'm not used to it's interface).
Hope that helps.
There was a change in the chrome debugging API that prevents VS from inspecting the elements and changing the style. Chrome version 43 will work. You have to take some steps to keep it from auto updating. The installer for chrome 43 is here:
https://dl.google.com/chrome/win/4ED6DD719811795B/43.0.2357.134_chrome_installer.exe
You will need to uninstall chrome, update the registry, then install chrome 43. When you go to the about screen it should say updates have been disabled by the administrator.
Here are the registry changes:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Update]
"Update{8A69D345-D564-463C-AFF1-A69D9E530F96}"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Google\Update]
"Update{8A69D345-D564-463C-AFF1-A69D9E530F96}"=dword:00000000
This thread has more information on the changes needed to the registry to prevent the auto update:
cannot stop Chrome from updating from 43 to 44
NOTE: this means you are not getting security updates on that install, only use this until the issue has been resolved in an upcoming patch.
I installed TortoiseHg (Mercurial) in my Vista 64-bit and the context menu is not showing up when I right click a file or folder.
Is there any workaround for this problem?
Update: TortoiseHg 0.8 (released 2009-07-01) now includes both 32 and 64 bit shell extensions in the installer, and also works with Windows 7. The workaround described below is no longer necessary.
A workaround to getting the context menus in Windows Explorer is buried in the TortoiseHg development mailing list archives. One of the posts provides this very handy tip on how to run 32-bit Explorer on 64-bit Windows:
TortoiseHG context menus will show up if you run 32-bit windows explorer; create a shortcut with this (or use Start > Run):
%Systemroot%\SysWOW64\explorer.exe /separate
(Source: http://www.mail-archive.com/tortoisehg-develop#lists.sourceforge.net/msg01055.html)
It works fairly well and is minimally invasive, but unfortunately this doesn't seem to make the icon overlays appear. I don't know of any workaround for that, but file status can still be viewed through TortoiseHg menu commands at least. All other TortoiseHg functionality seems intact.
The icon overlays are now working with TortoiseHg 0.6 in 32-bit explorer! Not sure if this is a new fix or if I had some misconfiguration in 0.5; regardless this means TortoiseHg is fully functional in 64-bit Windows.
In order to be able to use an extension in Explorer, the "bitness" of the extension needs to match the bitness of the operating system. This is because (at least under Windows) you can't load a 32-bit DLL into a 64-bit process -- or vice versa. If there's no 64-bit version of HgTortoise, then you can't use it with Explorer on a 64-bit Windows OS.
I upgraded to Windows 7 RC and the 64bit workaround seems to have stopped working
You could always install the command line hg and use it in a pinch. It's a bit faster, too.
I can verify that xplorer2 does show the HG tortoise context menu in 64bit Vista.
As detailed in the TortoiseHg FAQ, you need to run a 32-bit Windows Explorer instance for the context menu and overlays to work under 64-bit Vista.
My personal preference is to create a shortcut similar to the following for each project I'm actively using with TortoiseHg:
%windir%\syswow64\explorer.exe /separate /root,C:\projects\frobnicator
This launches explorer with the C:\projects\frobnicator folder already opened. (You can omit the /root option and just use the same shortcut for all projects if you don't mind clicking your way to the target folder every time you launch it.)
According to the TortoiseHg FAQ the context menus will work in 64-bit Vista if you start a 32-bit instance of explorer by creating a shortcut with the following settings (as suggested in the answer above):
Target: %windir%\syswow64\explorer.exe /separate
Start In: %windir%\syswow64\
I've just noticed that the context menu and icons work from a file open dialog from some apps (on Vista). I now just use Notepad++'s file open dialog, since I use Notepad++ all the time.
It seems to have to be the simple open dialog, not the new one Notepad has, for example.
Maybe someone can check if this trick works in Windows 7.