Ubuntu chrome graphic crash with developer tools - google-chrome

Very offen I have graphic crash when I use developer tools in chrome (41.0.2272.118 (64-bit) ) ubuntu 14.04, Radeon HD 7520G AMD fglrx(proprietary drivers). When I refresh page, some little time bihevior normal, after I get problem again.
In firefox all is normal.
UPD

Related

wikipedia page 100% CPU usage (one-thread, chrome/chromium only (not firefox))

https://en.wikipedia.org/wiki/List_of_mathematical_symbols
This page above has 100% cpu usage in Chrome/Chromium (one thread).
Can anybody duplicate the above?
Any web experts able to explain the above?
Seen on on two x86/AMD64 platforms that I tried. The first is Windows+Nvidia GPU Google-official Chrome and the second is Linux + AMD GPU + ubuntu-snap chromium.
This does not happen in Firefox on the Linux machine.
I cannot get the exact version information from windows at the moment but it is the 2004 (year 2020) build of Windows 10 Home 64bit and the latest version of Google Chrome.
The Linux version information is below.
Chromium:
Version 83.0.4103.116 (Official Build) snap (64-bit)
I am running a only two extensions: https everywhere, ublock origin.
Firefox (that does not have the problem):
78.0.2 (64-bit)
OS: Ubuntu 20.04 focal
Kernel: x86_64 Linux 5.4.0-40-generic
Uptime: 3d 20h 51m
Packages: 2785
Shell: bash 5.0.17
Resolution: 1920x1080
DE: KDE 5.68.0 / Plasma 5.18.5
WM: KWin
I have tried doing a performance recording, but I did not find the root cause.
https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/reference

Chrome Version 46.0.2490.71 (64-bit), developer tool not launching

My Chrome automatically updated itself to Version 46.0.2490.71 (64-bit) today 10/14/15, and it looks like the developer tool is broken – it can not be launched.
I uninstalled Chrome latest, and installed Version 45, the developer tool is working fine. But then Chrome immediately upgrades itself to Version 46 again.
I tried to stop the auto upgrade of Chrome by: defaults write com.google.Keystone.Agent checkInterval 0
that does not seem to have any effect – Chrome still tried to auto-upgrade itself.
Is there anyone else using Chrome latest and have the same issue?

How do you install flash debug version with Windows 10

I have been looking for a way to install the debug version of flashplayer for ie11 or the newer microsoft edge browser under Windows 10. AS far as I understand, the flash plugin is now embedded with both browsers, so there is no way to update it to a debug version.
Using the debug version installer from adobe site (active x version), gives me a pop-up stating that I already have the latest verion which is true, but there seems to be no way to change my version with the debug one.
AS anyone succeed in using the debug version of flash undex one of these browser on Windows 10 (64bits)?
Thanks,
Currently the answer is no, you can not use the Flash debugger in Windows 10 / IE or Edge browsers as they are 'embedded' libraries in the OS now. The options are to use Win 10 & Firefox or use Win 8.1 when debugging Flash.
Via: https://forums.adobe.com/message/7841726#7841726
I have received confirmation that at this time Microsoft does not
support the debuggers on Windows 10. We do not have an estimate as to
when they will support the debuggers, but when they do, the install
links will be added to the Adobe Flash Player Support Center page.
You might do it manually by yourself, the core step is running flash_debugger installation file with switch -install, after a few modification in debugger folder, then you might reach there.
showing the happy result in image following.enter image description here
Download the windows 7 virtual machine for free. I recommend Virtual Box. https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/
Once you have Windows 7 running inside Windows 10, install the IE Flash debugger or another of your choice. https://www.adobe.com/support/flashplayer/debug_downloads.html
IE 11 does not support flash player content debugging in windows 10.Fire fox and Chrome browsers however allow for the content debugging in windows 10.
1)Install Flash debugger for Firefox or Chrome:
a) Go to https://www.adobe.com/support/flashplayer/debug_downloads.html
b) For fire fox, Download and install Download the Flash Player content debugger for Firefox - NPAPI
c) For Chrome, Download and install Download the Flash Player content debugger for Opera and Chromium based applications – PPAPI

How to use software webgl engine in Chrome 18

I'd like to test out the new SwiftShader-based software WebGL engine which is allegedly in Chrome 18. I'm running 18.0.1025.165 on Mac OS X 10.7.3. I tried this command line (suggested here), but when I visit something with WebGL, it just says that it is disabled:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --blacklist-accelerated-compositing --blacklist-webgl
Is SwiftShader in the Mac version of Chrome 18? Is there a different trick I should use to enable it?
Currently SwiftShader is only available for Chrome under Windows. Is there any particular reason why you need it on Mac OS? Apple typically has adequate graphics hardware and OpenGL drivers.

WebGL doesn't work under Chrome in Windows 8 Developer Preview

Hi I was wondering if anyone else was having problems running WebGL in Windows 8 under Chrome.
I'm using Windows 8 Developer Preview x64 and Chrome 18. My video card is a Nvidia 250 GTS.
If I try to run any WebGL page, running though javaScript or NativeClient both fail to load thinking my video card doesn't support it.
I have my own native OpenGL apps that use GL2 and GL3 API features... GL itself is not the issue, unless I don't understand how Chrome uses GLES2 features.
Are there any known bugs about this?? Can't find anything.
EDIT: I just installed 'Windows 8 Consumer Preview x64' and WebGL still does not work... Is there a black list of OS's, kinda like some Intel video cards are black listed?? I have my system dual booted with Arch Linux and WebGL works fine on there?
As a workaround on windows 8 just add --disable-gpu-sandbox (I've checked it on 18 and 19 versions). To check open chrome://gpu/
For more information see chromium issue