Crash after crash - No idea what is causing it.

bobman

@Hadden89 said in Crash after crash - No idea what is causing it.:

vivaldi://flags

Dont think ive changed anything, but can reset it.

ok, trying to delete those extensions. mayve install older version of vivaldi and see.

DoctorG

@bobman said in Crash after crash - No idea what is causing it.:

mayve install older version of vivaldi and see.

Do not use profile from newer Vivaldi versions with older ones! Downgrade cracks profiles and cause unexpected issues which can not be fixed by us.

bobman

created a new user for vivaldi and sync, imported bookmarks+passwords. So lets see how long that last.

bobman

I also had plenty crashes and dead birds. Then it got better from Vivaldi.6.7.3329.29..

now the latest the crashes and dead birds are back, same few extensions. Tried the snapshot as standalone and it crashes also, must hate my asus pn53

WildEnte

@bobman did you try the troubleshooting steps, in particular step 3 (different clean profile) and 9 (hardware acceleration)?
https://help.vivaldi.com/desktop/troubleshoot/troubleshooting-issues/

bobman

@WildEnte said in Sadly, I will be leaving Vivaldi...BUT NOW I'm back after some fixes.:

@bobman did you try the troubleshooting steps, in particular step 3 (different clean profile) and 9 (hardware acceleration)?
https://help.vivaldi.com/desktop/troubleshoot/troubleshooting-issues/

yes , im doing that again.
made a thread with crashes etc on 6.7.3329.24. Then after 2-3 updates the crashes stopped. After the latest update they came back again. Did send in multiple reports. Also made new account for sync

bobman

ok, these crashes are driving me .... constant.
after creating this thread 2-3 updates came and no crashes. Then latest update and its constant again.

disabled extensions, tried with and without hardware acc. new sync profile. also reset win 11. (it was time) and new install, same thing. Dead bird then restart.

Was goinf to submit crash report, but guess what happened before i could send..

Graphics Feature Status
=======================
*   Canvas: Hardware accelerated
*   Canvas out-of-process rasterization: Enabled
*   Direct Rendering Display Compositor: Disabled
*   Compositing: Hardware accelerated
*   Multiple Raster Threads: Enabled
*   OpenGL: Enabled
*   Rasterization: Hardware accelerated
*   Raw Draw: Disabled
*   Skia Graphite: Disabled
*   Video Decode: Hardware accelerated
*   Video Encode: Hardware accelerated
*   Vulkan: Disabled
*   WebGL: Hardware accelerated
*   WebGL2: Hardware accelerated
*   WebGPU: Hardware accelerated
*   WebNN: Disabled

Driver Bug Workarounds
======================
*   disable_d3d11_vp9_ksvc_decoding
*   disable_direct_composition_sw_video_overlays
*   disable_nv12_dynamic_textures
*   disable_vp_auto_hdr
*   disable_vp_super_resolution
*   enable_webgl_timer_query_extensions
*   exit_on_context_lost
*   limit_d3d11_video_decoder_to_11_0
*   use_empty_video_hdr_metadata
*   disabled_extension_GL_KHR_blend_equation_advanced
*   disabled_extension_GL_KHR_blend_equation_advanced_coherent
*   disabled_extension_GL_MESA_framebuffer_flip_y

Problems Detected
=================
*   Some drivers are unable to reset the D3D device in the GPU process sandbox
    Applied Workarounds: exit_on_context_lost

*   Disable KHR_blend_equation_advanced until cc shaders are updated:
    (http://crbug.com/661715)
    Applied Workarounds: disable(GL_KHR_blend_equation_advanced),
        disable(GL_KHR_blend_equation_advanced_coherent)

*   Expose WebGL's disjoint_timer_query extensions on platforms with site isolation:
    (http://crbug.com/808744), (http://crbug.com/870491)
    Applied Workarounds: enable_webgl_timer_query_extensions

*   Disable GL_MESA_framebuffer_flip_y for desktop GL:
    (http://crbug.com/964010)
    Applied Workarounds: disable(GL_MESA_framebuffer_flip_y)

*   dynamic textures fail to work on AMD GPUs:
    (http://crbug.com/1029855), (http://crbug.com/1050666)
    Applied Workarounds: disable_nv12_dynamic_textures

*   Limit D3D11VideoDecoder to 11.0 due to crashes on AMD:
    (http://crbug.com/1012464)
    Applied Workarounds: limit_d3d11_video_decoder_to_11_0

*   Send empty video hdr metadata due to crashes on AMD:
    (http://crbug.com/1045586)
    Applied Workarounds: use_empty_video_hdr_metadata

*   Software overlays fail to work reliably on AMD devices:
    (http://crbug.com/1161215), (http://crbug.com/1160217)
    Applied Workarounds: disable_direct_composition_sw_video_overlays

*   Only enable video processor super resolution on Intel Gen10+ GPUs and NVIDIA GPUs with 530+ drivers:
    (http://crbug.com/1318380)
    Applied Workarounds: disable_vp_super_resolution

*   Only enable video processor auto HDR on NVIDIA GPUs with 550.50+ driver:
    (http://crbug.com/1445741)
    Applied Workarounds: disable_vp_auto_hdr

*   Disable VP9 k-SVC video decoding on non-Intel GPUs:
    (http://crbug.com/1508379)
    Applied Workarounds: disable_d3d11_vp9_ksvc_decoding

yngve

@bobman I had a look through your reported crashes from a month ago. All of them were related to the Blink code in Chromium (the page display code).

Given some aspects of those crashes (they were effectively caused by null pointers), I am wondering the crashes as caused by out of memory (OOM) events. That is, I am wondering if they are caused by your machine not having enough memory available to display the pages you are loading. You might want to look at the memory specs and usage of your machine (E.g by looking at the Windows Task Manager performance tab).

Additionally, I see that there are several changes in the Blink code in the various minor updates during the past month. It could be that those solved the crashes you reported previously.

However, I would like to caution you: DO NOT(!) assume that just because you now have another set of crashers that they are "the same" as the the ones you reported a month ago. They may be caused by something completely different. Only a bug report with crash dump can let us determine that.

bobman

thanks for getting back to me.
I have 32GB of ram, and now have vivaldi open with 15 tabs and running cinebench and currently using 54% memory.

so its not that. Did memory + and windows memory test with no errors. So maybe its a chrome thing behind the crashes.

on a reset win 11 now, sonot much more I could do.

yngve

@bobman OK, one thing that often happens during OOM is that null pointers are created, and causes a crash a bit later.

I had an extra look at one of your earlier crash reports, and noticed that you at the time had 7 extensions installed (and I see you listed them above). Extensions (as mentioned above) are known to occasionally cause problems, which is why all the volunteers troubleshooting tips have various entries for testing them.

bobman

Well, I've reinstalled win 11 3 times now, and Vivaldi, edge etc crash on acess violation. Fresh updated install.

So, possible a hw problem here

yngve

@bobman Well, if you have multiple applications (or at least browsers) crashing, it is rather unlikely to a Vivaldi-specific issue. It could be a general Chromium issue, but only crashdumps can determine that.

If you have problems with other apps, then you might need to look elsewhere for reasons, and in that case hardware, especially RAM errors might be candidates.

bobman

@yngve well, i think I finally found my issue.

If I use all cores vivaldi and chrome based browsers crash like crazy. set affinity and only using 1 core, no crash and plenty extensions and tabs open. So seems a core issue on my cpu

yngve

@bobman Ouch! I suggest replacing it ASAP.

OK, that could explain why all of your crashlogs were all over the place.