New issue
Advanced search Search tips

Issue 863265 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 29
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chromium fails to load page

Reported by singh.ha...@gmail.com, Jul 13

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce the problem:
I am using CefSharp library to use headless chromium for taking screenshots of our website. As our request load to take screenshot increases, Chromium fails to load website.

What is the expected behavior?

What went wrong?
Error seen in CEF logs:

[0626/201333.214:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service: C:\WFRoot\SBRole.3\Fabric\work\Applications\ASAzureApp_App0\ScreenshotServicePackage.ScreenshotService.Code.06.3_13.0.5702.156_1806221821\content_renderer.service.exe 

What is the service used for and how could this issue be resolved?

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 65.0.3325.181  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 30.0 r0
 
Labels: Needs-Milestone
Cc: vamshi.kommuri@chromium.org
Components: Internals>Services>ServiceManager
Labels: Triaged-ET Needs-Feedback
Thanks for filing the issue!

@Reporter: Could you please check the same by updating chrome to the latest version and let us know if the issue still persists. Please find the below link to download/install chrome latest version(s). Tentatively adding component "Internals>Services>ServiceManager" due to 'ERROR:service_manager_context.cc' in the log provided in C#0 and requesting someone from respective team to have a look into this.
https://www.chromium.org/getting-involved/dev-channel
Status: WontFix (was: Unconfirmed)
As there isn't any Feedback from reporter since long time, closing this issue and marking it as Won't Fix.

@Reporter: Requesting you to file/raise a new issue if this happens in latest chrome versions.

Thanks!

Sign in to add a comment