Vivaldi uses 80% CPU
-
@lamarca & @Gwen-Dragon - I ran vivaldi://gpu as requested. Results below, hope you can figure out how I can get my Vivaldi back!
Thanks,
John
Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Out-of-process Rasterization: Disabled
Hardware Protected Video Decode: Unavailable
Rasterization: Hardware accelerated
Skia Deferred Display List: Disabled
Skia Renderer: Disabled
Surface Control: Disabled
Surface Synchronization: Enabled
Video Decode: Hardware accelerated
Viz Service Display Compositor: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
Driver Bug Workarounds
clear_uniforms_before_first_program_use
decode_encode_srgb_for_generatemipmap
disable_accelerated_vpx_decode
disable_discard_framebuffer
disable_framebuffer_cmaa
disable_larger_than_screen_overlays
exit_on_context_lost
force_cube_complete
msaa_is_slow
scalarize_vec_and_mat_constructor_args
disabled_extension_GL_KHR_blend_equation_advanced
disabled_extension_GL_KHR_blend_equation_advanced_coherent
Problems Detected
Older Intel GPUs cannot support protected video decoding in swap chains
Disabled Features: protected_video_decode
Some drivers are unable to reset the D3D device in the GPU process sandbox
Applied Workarounds: exit_on_context_lost
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
ANGLE crash on glReadPixels from incomplete cube map texture: 518889
Applied Workarounds: force_cube_complete
On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
Applied Workarounds: msaa_is_slow
Framebuffer discarding can hurt performance on non-tilers: 570897
Applied Workarounds: disable_discard_framebuffer
Use GL_INTEL_framebuffer_CMAA on ChromeOS: 535198
Applied Workarounds: disable_framebuffer_cmaa
Disable KHR_blend_equation_advanced until cc shaders are updated: 661715
Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent)
Decode and Encode before generateMipmap for srgb format textures on Windows: 634519
Applied Workarounds: decode_encode_srgb_for_generatemipmap
Accelerated VPx decoding is hanging on some videos.: 654111
Applied Workarounds: disable_accelerated_vpx_decode
Overlay sizes bigger than screen aren't accelerated on some Intel drivers: 720059
Applied Workarounds: disable_larger_than_screen_overlays
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers
Viz service display compositor is not enabled by default.
Disabled Features: viz_display_compositor
Skia renderer is not used by default.
Disabled Features: skia_renderer
Skia deferred display list is not used by default.
Disabled Features: skia_deferred_display_list
Version Information
Data exported 2019-02-18T10:18:33.721Z
Chrome version Chrome/72.0.3626.110
Operating system Windows NT 10.0.17763
Software rendering list URL https://chromium.googlesource.com/chromium/src/+/38c6381358a1ec7a9fc161a038fb9d7407334aa4/gpu/config/software_rendering_list.json
Driver bug list URL https://chromium.googlesource.com/chromium/src/+/38c6381358a1ec7a9fc161a038fb9d7407334aa4/gpu/config/gpu_driver_bug_list.json
ANGLE commit id unknown hash
2D graphics backend Skia/72 7a1e00421d97a1f4f171dd2a8f817f9b07c9cdfd-
Command Line "C:\Users\john\AppData\Local\Vivaldi\Application\vivaldi.exe" --flag-switches-begin --flag-switches-end --save-page-as-mhtml
Driver Information
Initialization time 662
In-process GPU false
Passthrough Command Decoder false
Sandboxed true
GPU0 VENDOR = 0x8086 [Google Inc.], DEVICE= 0x0152 [ANGLE (Intel(R) HD Graphics Direct3D11 vs_5_0 ps_5_0)] ACTIVE
Optimus false
AMD switchable false
Desktop compositing Aero Glass
Direct composition true
Supports overlays false
Overlay capabilities
Driver D3D12 feature level Not supported
Driver Vulkan API version Not supported
Driver vendor Intel Corporation
Driver version 10.18.10.4252
Driver date 7-10-2015
GPU CUDA compute capability major version 0
Pixel shader version 5.0
Vertex shader version 5.0
Max. MSAA samples 8
Machine model name
Machine model version
GL_VENDOR Google Inc.
GL_RENDERER ANGLE (Intel(R) HD Graphics Direct3D11 vs_5_0 ps_5_0)
GL_VERSION OpenGL ES 2.0 (ANGLE 2.1.0.unknown hash)
GL_EXTENSIONS GL_ANGLE_client_arrays GL_ANGLE_depth_texture GL_ANGLE_explicit_context GL_ANGLE_explicit_context_gles1 GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_memory_size GL_ANGLE_multi_draw GL_ANGLE_multiview_multisample GL_ANGLE_pack_reverse_row_order GL_ANGLE_program_cache_control GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_color_buffer_float_rgb GL_CHROMIUM_color_buffer_float_rgba GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_sync_query GL_EXT_blend_minmax GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_frag_depth GL_EXT_map_buffer_range GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_bptc GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_KHR_parallel_shader_compile GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_border_clamp GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object OES_compressed_EAC_R11_signed_texture OES_compressed_EAC_R11_unsigned_texture OES_compressed_EAC_RG11_signed_texture OES_compressed_EAC_RG11_unsigned_texture OES_compressed_ETC2_RGB8_texture OES_compressed_ETC2_RGBA8_texture OES_compressed_ETC2_punchthroughA_RGBA8_texture OES_compressed_ETC2_punchthroughA_sRGB8_alpha_texture OES_compressed_ETC2_sRGB8_alpha8_texture OES_compressed_ETC2_sRGB8_texture
Disabled Extensions GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent
Disabled WebGL Extensions
Window system binding vendor Google Inc. (adapter LUID: 000000000000888c)
Window system binding version 1.4 (ANGLE 2.1.0.unknown hash)
Window system binding extensions EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_ANGLE_direct_composition EGL_ANGLE_windows_ui_composition EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_EXT_device_query EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_stream_producer_d3d_texture EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_CHROMIUM_sync_control EGL_EXT_pixel_format_float EGL_KHR_surfaceless_context EGL_ANGLE_display_texture_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_program_cache_control EGL_ANGLE_robust_resource_initialization EGL_ANGLE_create_context_extensions_enabled EGL_ANDROID_blob_cache
Direct rendering Yes
Reset notification strategy 0x8252
GPU process crash count 0
Compositor Information
Tile Update Mode One-copy
Partial Raster Enabled
GpuMemoryBuffers Status
R_8 Software only
R_16 Software only
RG_88 Software only
BGR_565 Software only
RGBA_4444 Software only
RGBX_8888 GPU_READ, SCANOUT
RGBA_8888 GPU_READ, SCANOUT
BGRX_8888 Software only
BGRX_1010102 Software only
RGBX_1010102 Software only
BGRA_8888 Software only
RGBA_F16 Software only
YVU_420 Software only
YUV_420_BIPLANAR Software only
UYVY_422 Software only
Display(s) Information
Info Display[2528732444] bounds=[0,0 1280x960], workarea=[0,0 1280x899], scale=1.25, external.
Color space information {primaries:BT709, transfer:IEC61966_2_1, matrix:RGB, range:FULL}
Bits per color component 8
Bits per pixel 24
Video Acceleration Information
Decode h264 baseline up to 1920x1088 pixels
Decode h264 main up to 1920x1088 pixels
Decode h264 high up to 1920x1088 pixels
Encode h264 baseline up to 3840x2176 pixels and/or 30.000 fps
Encode h264 main up to 3840x2176 pixels and/or 30.000 fps
Encode h264 high up to 3840x2176 pixels and/or 30.000 fps
Diagnostics
0
b3DAccelerationEnabled true
b3DAccelerationExists true
bAGPEnabled true
bAGPExistenceValid true
bAGPExists true
bCanRenderWindow true
bDDAccelerationEnabled true
bDriverBeta false
bDriverDebug false
bDriverSigned false
bDriverSignedValid false
bNoHardware false
dwBpp 32
dwDDIVersion 11
dwHeight 1200
dwRefreshRate 60
dwWHQLLevel 0
dwWidth 1600
iAdapter 0
lDriverSize 11053040
lMiniVddSize 0
szAGPStatusEnglish Enabled
szAGPStatusLocalized Enabled
szChipType Intel(R) HD Graphics Family
szD3DStatusEnglish Enabled
szD3DStatusLocalized Enabled
szDACType Internal
szDDIVersionEnglish 11.2
szDDIVersionLocalized 11.2
szDDStatusEnglish Enabled
szDDStatusLocalized Enabled
szDXVAHDEnglish Supported
szDXVAModes ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C
szDescription Intel(R) HD Graphics
szDeviceId 0x0152
szDeviceIdentifier {D7B78E66-4212-11CF-6F63-47A4B4C2C735}
szDeviceName \.\DISPLAY1
szDisplayMemoryEnglish 1792 MB
szDisplayMemoryLocalized 1792 MB
szDisplayModeEnglish 1600 x 1200 (32 bit) (60Hz)
szDisplayModeLocalized 1600 x 1200 (32 bit) (60Hz)
szDriverAssemblyVersion 10.18.10.4252
szDriverAttributes Final Retail
szDriverDateEnglish 7/9/2015 7:00:00 PM
szDriverDateLocalized 7/9/2015 19:00:00
szDriverLanguageEnglish English
szDriverLanguageLocalized English
szDriverModelEnglish WDDM 1.3
szDriverModelLocalized WDDM 1.3
szDriverName igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll
szDriverNodeStrongName oem3.inf:5f63e534c477ad23:iIVBD_w81:10.18.10.4252:pci\ven_8086&dev_0152
szDriverSignDate Unknown
szDriverVersion 10.18.0010.4252
szKeyDeviceID Enum\PCI\VEN_8086&DEV_0152&SUBSYS_844D1043&REV_09
szKeyDeviceKey \Registry\Machine\System\CurrentControlSet\Control\Video{D76079FE-23D0-11E9-86B6-BC92A9349D0F}\0000
szManufacturer Intel Corporation
szMiniVdd unknown
szMiniVddDateEnglish Unknown
szMiniVddDateLocalized unknown
szMonitorMaxRes Unknown
szMonitorName Unknown
szNotesEnglish No problems found.
szNotesLocalized No problems found.
szOverlayEnglish Supported
szRankOfInstalledDriver 00DA2001
szRegHelpText Unknown
szRevision Unknown
szRevisionId 0x0009
szSubSysId 0x844D1043
szTestResultD3D7English Not run
szTestResultD3D7Localized Not run
szTestResultD3D8English Not run
szTestResultD3D8Localized Not run
szTestResultD3D9English Not run
szTestResultD3D9Localized Not run
szTestResultDDEnglish Not run
szTestResultDDLocalized Not run
szVdd unknown
szVendorId 0x8086
Log Messages
GpuProcessHostUIShim:
GpuProcessHostUIShim: -
@Ayespy & @lamarca - I know it isn't a resource hog generally, otherwise every single posting here would be about it. My guess is that there is a driver issue with Windows 10 on my ASUS M11 (this machine) and my Lenovo X220 laptop.
Thanks for your help, I have posted the results from vivaldi://gpu and tagged @Gwen-Dragon...
John
-
@Gwen-Dragon said in Vivaldi uses 80% CPU:
Did you try after a profile reset, i.e. with no installed extensions and changes of Vivaldi settings?
Using the instructions I was given, I uninstalled Vivaldi, rebooted the computer, reinstalled it, rebooted again. That did not fix the issue.
-
These instructions: https://help.vivaldi.com/article/uninstall-vivaldi-on-windows-10/
-
@johnm243
Hi, iirc uninstall does not overwrite your profile, check https://forum.vivaldi.net/topic/10388/refreshing-or-cleaning-your-profileCheers, mib
-
@Gwen-Dragon said in Vivaldi uses 80% CPU:
Have a profile reset, i.e. with no installed extensions and changes of Vivaldi settings
Thanks @Gwen-Dragon, I did that last night and ran it overnight. All is good, CPU is normal!
Check you have the latest chipset and graphics drivers from your hardware manufacturers website (Windows 10 store has not always the correct one)?
I just downloaded the Intel Driver and Support Assistant Installer from the Intel website. I will install the most recent drivers.
Once that is done, can I log into Vivaldi and sync down my settings? Or is there something else you suggest I do first?
Thanks very much,
John
-
@Gwen-Dragon thanks. FYI, the Intel HD Graphics 2500 drivers upgraded from v. 10.18.10.4252 to v. 10.18.10.5059.
Let me sync my settings now, hope I get my Vivaldi back!
John
-
@Gwen-Dragon Vivaldi is still using a huge amount of CPU! It doesn't take over my computer like before -- I had to use the power switch several times while I tried to figure out the cause of the problem -- but it is still using way too much CPU and RAM! RAM isn't nearly 3 GB like before -- but over 2 GB is quite a lot for one app!
Any other ideas?
Thanks very much,
John
-
I just want to provide a 2nd perspective on this issue that this happens on linux as well, and the only process using between 50% to 100% of my CPU is the Browser process itself.
for me, this doesn't happen initially after launching the browser (excluding load-up of course), but after some time when the browser goes idle, it'll spike, and I'll be forced to close the browser.
I've tried killing the offending process in System Monitor, which doesn't crash the browser, but any further attempts to load new pages causes the new page to hang indefinitely and never load.
I've been trying to find the cause of this issue for months, and it's difficult to put my finger on...
I don't believe extensions are the problem as everything else works as expected...is there any way to get more verbose information as to what the Browser process could be doing when this happens??
-
One of the above pictures shows 33 processes.!.that can't be right surely.?
I would suggest the op totally removes vivaldi and all associated profiles etc and start from scratch.
-
I guess mostly the reason is because some opened 100+ Tabs.
Ok; try. But not be surprised if your system says goodbye.
-
@Ice007 actually, Vivaldi is REALLY good on memory, especially when you hibernate tabs
I just recently got some extra DDR3 from a friend which boosted this machine to 4GB, and even with 40+ tabs open, I'm not even using 2GB.
that even beats Firefox.but yeah I'm kinda cheating to beat FF by hibernating tabs XD
also @Priest72 isn't that a bit much of a suggestion
I mean I know Vivaldi has a horrible time remembering login info for sites, but if someone's actually reliant on their profile for bookmarks and such, wouldn't it be best NOT to ask them to delete all that?
(the only exception there is a corrupted profile you can't recover from) -
@Priest72 said in Vivaldi uses 80% CPU:
One of the above pictures shows 33 processes.!.that can't be right surely.?
I would suggest the op totally removes vivaldi and all associated profiles etc and start from scratch.
Depending on how the user has the browser configured, and how many different sites are open, 33 processes would be expected. Chromium uses a multi-process architecture in order to isolate the render process for different sites from each other. This makes it bother safer and more robust than a monolithic architecture in which a compromised or or hung render process from one site would affect the whole browser.
Chromium used to have an upper limit of about 80 processes, depending on the amount of RAM on the system. That may have changed when strict site isolation was implemented and could be higher in general, or only when using strict site isolation. In not certain as I haven't dug into those details yet. Perhaps some day, given free time or work requirements.
So given that, I don't think there's necessarily anything unexpected occurring in that screenshot, and a clean install may have no effect. I think more likely, it's just necessary to educate users on the design of Chromium-based browsers. Each site is likely to have its own process, or each tab of the user configured it to work that way, as well as each active plug-in. This does increase memory use, but as I mentioned above, Chromium has an upper limit on the processes depending on the available memory.
It is possible to run Chromium-based browsers in a single monolithic process, but that should never be done for your daily browsing, it's just available for testing purposes. In such a configuration, a crash in any site's render process would affect the entire browser.
-
@Tcll said in Vivaldi uses 80% CPU:
I've tried killing the offending process in System Monitor, which doesn't crash the browser, but any further attempts to load new pages causes the new page to hang indefinitely and never load.
Please - do not terminate the main browser process and do not terminate browser processes with outside programs! Try instead to focus on finding the site/tab that's causing this CPU load. A good way would be to close tabs one by one until the CPU usage goes away.
There are ways to try to figure out what a process is doing, by looking at its threads or what kinds of operations it performs (IO, network etc). I would assume this is even easier on Linux than on Windows, with all the wonderful command-line process tools available. However, obviously this would require a certain level of technical knowledge.
I would advise that instead of digging up two year old threads (from someone with a completely different OS no less), you open a new thread in the relevant forum and someone will be along to help you.
-
@Pathduck said in Vivaldi uses 80% CPU:
A good way would be to close tabs one by one until the CPU usage goes away.
it doesn't, neither hibernating nor closing the tab stops the usage.
once the issue starts (it doesn't matter what tab I'm on)
the only solution so far is to restart the browserI don't believe it's a site that causes the issue
I've had it randomly start up just from sitting idle on a small PHP-BB (noob-level, low resource) forum (being the only active tab not in hibernation)
I believe it's a browser issue that just happens randomly.also yeah, it's nothing from the network, my particular issue is entirely on the CPU
I'm actually wondering if the op's issue is similaralso, I wasn't looking for personal help, or yes, I'd do just that
I was only trying to provide an alternate perspective to hopefully help solve or give insight on an issue.EDIT: also, I came here from DDG
I didn't dig up this thread -
@Ice007 said in Vivaldi uses 80% CPU:
I guess mostly the reason is because some opened 100+ Tabs.
Ok; try. But not be surprised if your system says goodbye.
I regularly use over 100 tabs without issue, including on systems with no virtual memory. I haven't upgraded my workstation hardware in over 4 years, half the memory slots are empty and there certainly are better processors I could swap into the motherboard. So it doesn't require the latest & greatest hardware. Though I'm sure there are resource limited systems that can't handle lots of tabs, even on my 7 year-old laptop, which wasn't top of the line when new, still can easily handle dozens of tabs.
Vivaldi itself is more than capable of handling that many tabs. It's really not the number of tabs that tax your system anyways, it's the content in those tabs. A single poorly coded website is sufficient to max out the CPU. The amount of RAM used is similarly going to be influenced by the content. The multiple process architecture of Chromium does consume more memory than a monolithic architecture would, but it's done for good reason.
-