Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

File downloads crash Brave on Windows Server Core #9435

Closed
lewellyn opened this issue Jun 14, 2017 · 4 comments · Fixed by #11906
Closed

File downloads crash Brave on Windows Server Core #9435

lewellyn opened this issue Jun 14, 2017 · 4 comments · Fixed by #11906

Comments

@lewellyn
Copy link

lewellyn commented Jun 14, 2017

Test plan

#11906 (comment)


  • Did you search for similar issues before submitting this one?
    Yes

  • Describe the issue you encountered:
    File downloads crash the browser.

  • Platform (Win7, 8, 10? macOS? Linux distro?):
    Windows Server 2016 Core (specifically, Windows Hyper-V Server 2016)

  • Brave Version (revision SHA):
    fba98fc

  • Steps to reproduce:

    1. Visit a page with a file download link.
    2. Click the download link.
  • Actual result:
    Browser crashes without any dialog or other grace.

  • Expected result:
    File should download

  • Will the steps above reproduce in a fresh profile? If not what other info can be added?
    Yes.

  • Is this an issue in the currently released version?
    Yes.

  • Can this issue be consistently reproduced?
    Yes.

  • Extra QA steps:
    1.
    2.
    3.

  • Screenshot if needed:
    N/A

  • Any related issues:
    Potentially File picker does not function on Windows Server Core #9409

@srirambv
Copy link
Collaborator

Verified on Windows 10 but not on Windows Server

@bsclifton bsclifton modified the milestones: 0.22.x (Developer Channel), 0.21.x w/ Chromium 65 (Beta Channel) Mar 1, 2018
@bsclifton
Copy link
Member

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

@bsclifton bsclifton modified the milestones: 0.21.x w/ Chromium 65 (Beta Channel), 0.22.x (Developer Channel) Mar 9, 2018
@srirambv
Copy link
Collaborator

Verified on Windows x64

  • 0.22.6 e6ff4ea
  • libchromiumcontent: 65.0.3325.162
  • muon: 5.1.0

@kjozwiak
Copy link
Member

This issue will appear in the release notes via #10653 which has the same fix.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.