This is my cpu capture profile

Deleted: CPU-20170511T141136.cpuprofile 1.1 MB

CPU-20170511T141136.cpuprofile 1.1 MB Download

Thanks for logging the issue.

Please provide a sample testcase for the ease of triaging and crash id from chrome://crashes.

Hi ligim

in case it error on my customer browser and i can't get hash :-s.
My customer use chrome version 57 or 58 ?. 
Can has any bugs ?

Thanks

Thank you for providing more feedback. Adding requester "ligimole@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Noticed this problem on the following UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Multiple cases being reported to us.

Could you please provide us any sample test file or URL to reproduce the crash from our end.

Thanks,

@kavvaru - Initialising print dialogue on any website causes this problem. (CTRL + P)

Please try to get a crash report id: https://www.chromium.org/for-testers/bug-reporting-guidelines/reporting-crash-bug

Already put crash IDs in comment 6 but they were deleted.

Did you mean to give us a crash report ID but accidentally deleted it, or did you not want to give us a crash report ID, or did the bug reporting website delete it somehow? Feel free to email me if the bug reporting website is giving you trouble.

@thestig - The site removed them by the look of it.
I've dropped you an email with the crash IDs. Hopefully they help.

Maybe comment 6 incorrectly got flagged as spam? I don't know if that issue is the exact same issue as the bug reporter's. The crash ID is 947e880e40000000 and it's a crash inside printing::PrintingContextSystemDialogWin::ShowPrintDialog() in KOAZ8WAU.dll. I'm guessing that's part of a Konica printer driver? If so, what printer model is it for and what's the exact driver version?

We haven't heard back in several months, so I am going to archive this bug report. If you have info on the specific printer model + driver, we can reopen the bug and look into it.