"Save Image..." very often crashes the browser

[JaneSmith]

Test plan

#11906 (comment)

---

• Describe the issue you encountered:
  When I right-click on an image and choose "Save Image...", the save dialog appears. Sometimes this works fine. However, very often the browser will crash as the dialog window appears.

• Platform (Win7, 8, 10? macOS? Linux distro?):
  Windows 10 Pro.

• Brave Version (revision SHA):
  36ae2ec

• Steps to reproduce:

  1. Right-click on an image.
  2. Choose "Save Image..."

• Actual result:
  The browser crashes.

• Expected result:
  I should be able to save the image without issues.

• Can this issue be consistently reproduced?
  No.

I save images quite often. As a result, I'm experiencing browser crashes at least 20+ times a day, and then when I restart the browser I end up with a session from some time ago. There are various other bugs with Brave that I can overlook, but unfortunately this one is becoming way too big of an issue for me. I'm becoming very frustrated with the browser crashing constantly over and over and over and over again, and then as a result losing my open tabs, losing my position in videos, losing my current input into forms, losing my scroll position on long pages...

I love Brave for the clean and compact UI, the Shields system, and for being designed with privacy in mind... But sadly I am going to have to stop using it as my main browser until it becomes more stable. :(

[bsclifton]

@JaneSmith can you check out #3313? I'm curious if this is the same issue

[JaneSmith]

Hmm... I'm not sure. It sounds similar, but I can't reproduce the issue by following any of the steps listed on that bug report. I also never needed to Alt+Tab out in order to get this issue. It would just occur randomly when trying to save images, without me switching to another window.

[bsclifton]

Moving to 0.22.x; we're going to have 0.21.x-C65 only contain the Chromium upgrade 😄 👍

[srirambv]

Verified on Windows x64

• 0.22.6 e6ff4ea
• libchromiumcontent: 65.0.3325.162
• muon: 5.1.0

Verified that the above issue has been fixed on macOS 10.13.3 x64 using the following build:

• 0.22.6 e6ff4ea
• libchromiumcontent: 65.0.3325.162
• muon: 5.1.0

Verified on Ubuntu 10.10 x64

• 0.22.7 8bb7e77
• libchromiumcontent: 65.0.3325.181
• muon: 5.1.1