Vivaldi crashes when trying to open chrome passwords keystore



  • Vivaldi crashes when trying to open chrome passwords keystore, right after windows account password input
    chrome://settings/passwords


  • Moderator

    @le_bro said in Vivaldi crashes when trying to open chrome passwords keystore:

    chrome://settings/passwords

    Not crashing here. Are you using any extensions?


    Specs: AMD A10-6800K, 8 Gb on Win 10 64-bit •Snapshot 1.15.1147.19 (64-bit)


  • Moderator

    @pesala said in Vivaldi crashes when trying to open chrome passwords keystore:

    chrome://settings/passwords

    Could not reproduce such crash with 1.14.1077.60 Stable and 1.15.1147.19 Snapshot on my Windows 10.



  • turned off all extensions → restarted browser → chrome://settings/passwords → clicked on eye to show passwords → Windows user password dialogue appears, entered my password → clicked OK → Vivaldi crashed

    problem persists

    My rig: W7 Ultimate x64, 48 GB RAM, Xeon X5675, got adequate amount of free space on drives. Filesystem is OK.

     <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Application Error" /> 
      <EventID Qualifiers="0">1000</EventID> 
      <Level>2</Level> 
      <Task>100</Task> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2018-04-11T19:35:01.000000000Z" /> 
      <EventRecordID>1649616</EventRecordID> 
      <Channel>Application</Channel> 
      <Computer>-------</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data>vivaldi.exe</Data> 
      <Data>1.15.1147.19</Data> 
      <Data>5acdec69</Data> 
      <Data>ntdll.dll</Data> 
      <Data>6.1.7601.24000</Data> 
      <Data>5a499ad2</Data> 
      <Data>c0000374</Data> 
      <Data>00000000000bf6b2</Data> 
      <Data>59bc</Data> 
      <Data>01d3d1cbfd3533d2</Data> 
      <Data>C:\Vivaldi\Application\vivaldi.exe</Data> 
      <Data>C:\Windows\SYSTEM32\ntdll.dll</Data> 
      <Data>6cdf795e-3dbf-11e8-9cf7-005056c00008</Data> 
      </EventData>
      </Event>
    

  • Moderator

    Open vivaldi://flags in adress feld
    Reset all flags
    Restart Vivaldi



  • Resetted flags to default, result is same…

    PS: Only this flags were enabled by me:
    vivaldi://flags/#enable-site-per-process
    vivaldi://flags/#enable-quic
    vivaldi://flags/#save-page-as-mhtml


  • Moderator

    @le_bro site-per-process is known causing some problems on Chromium browsers.


  • Moderator

    @le_bro You should test without any extensions!
    Try to start vivaldi with a temporary clean profile
    C:\Vivaldi\Application\vivaldi.exe --user-data-dir="%TEMP%\VIVTEMP"
    Login to a page
    Store the password
    Open chrome internal password page
    Show the password with the click on eye
    Does that crash?

    If it crashes, then please report the issue.
    Please read How to Report a bug for Vivaldi carefully and then report the bug to Vivaldi bugtracker.
    And send us a crashdump as described in https://help.vivaldi.com/article/reporting-crashes-on-windows/



  • @Gwen-Dragon

    site-per-process is known causing some problems on Chromium browsers.

    Yes, but it is an important security measure in era of spectre and meltdown.

    You should test without any extensions!

    I did that without extensions. I mean before I disabled everything I had only those 4 flags manually enabled, but when I tested, I resetted them to default beforehand.

    Try to start vivaldi with a temporary clean profile
    C:\Vivaldi\Application\vivaldi.exe --user-data-dir="%TEMP%\VIVTEMP"
    Login to a page
    Store the password
    Open chrome internal password page
    Show the password with the click on eye
    Does that crash?

    It actually does.

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-04-16T05:32:49.000000000Z" />
    <EventRecordID>1650027</EventRecordID>
    <Channel>Application</Channel>
    <Computer>--------</Computer>
    <Security />
    </System>
    <EventData>
    <Data>vivaldi.exe</Data>
    <Data>1.15.1147.21</Data>
    <Data>5acf8a31</Data>
    <Data>ntdll.dll</Data>
    <Data>6.1.7601.24000</Data>
    <Data>5a499ad2</Data>
    <Data>c0000374</Data>
    <Data>00000000000bf6b2</Data>
    <Data>3b40</Data>
    <Data>01d3d544556cd459</Data>
    <Data>C:\Vivaldi\Application\vivaldi.exe</Data>
    <Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
    <Data>99523c95-4137-11e8-b1dc-005056c00008</Data>
    </EventData>
    </Event>



  • Update:

    This problem also occurs on Vivaldi 1.15.1147.32, Chrome 65.0.3325.181, SRWare Iron 65.0.3400.0.

    I've managed to view my passwords, but I can't call it a fix:

    Before attempting to view hidden passwords, go to Windows user account settings and remove password. Then reveal your desired passwords. After you done, restore your Windows password.

    Method sucks, but I can't find nothing better.

    PS: tried to reveal saved password on freshly created Windows account, and clean browser. Problem persists.



  • @le_bro said in Vivaldi crashes when trying to open chrome passwords keystore:

    This problem also occurs on Vivaldi 1.15.1147.32

    I can't reproduce the problem on Windows 10 Pro!?

    site-per-process is known causing some problems on Chromium browsers.
    Yes, but it is an important security measure in era of spectre and meltdown.

    I do NOT have this flag enabled. Causes too many crashes/freezes atm.


  • Moderator

    @le_bro Can't reproduce this. Works fine on Win10 Home



  • Sure thing most users can't reproduce this crash. It's rare, but if you search "chrome password crash" you will see: this problem exists for some users for years. Too bad Google developers are ignorant to fix bugs, tending to make new functions instead.

    PS: for ex. https://www.google.com/search?q=chrome reveal passwords crash


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.