[mac bug triage]
Hello,

What does "window freezes" mean, exactly? Do you get the spinning cursor? What's the dialog's behavior, exactly?

This should clear up the behavior
https://drive.google.com/file/d/1s2FJj4tTT4P90JERJNHwNQcg3TuF9wkm/view?usp=sharing

More often then not it takes less time then I did to get the behavior to
replicate

Thank you for providing more feedback. Adding requester "shrike@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

Thank you for your feedback. I tried to reproduce it on macOS 10.12.6, but I can't.

You are using a very old macOS version (10.10.5). Is your issue only reproducible on that version? Or do you see this also in newer macOS versions?

The bug reports reflected the OS this took place in. The original case of
the bug occurred in chrome version 58 and was fixed in version 62, for
10.10.5. Though both OS will sometimes display the "Aw Snap" window if
you're in that menu for sometime. It's odd to me that a bug that was fixed
has regressed again.

Regressions happen :-(

May be you can try to find the build number, when the issue started again.

You can do it manually here: https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac/

Or if you have Dev skills here: https://www.chromium.org/developers/bisect-builds-py

BTW: May be you attach the server crash id from chrome://crashes if it crashes again.

Thanks for your help!

If I have this number "62.0.3202.62" how does that translate on the two
pages provided

If you are searching for the changes between 62.0.3202.62 and 63.0.3239.84, you can try to find the culprit between build 499098 and 508578.

Because I am not a dev, I prefer to do it manually from https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac/

[Mac triage] very tentatively suspecting 24ab401b3662d052facf19a169f553ea9a6bf7e1. tapted@, what do you think?

Sorry, the actual commit I meant to flag was 41cf14577509cfb124b9b38038b913da8256ba07, but it's more this set of run loop changes as a whole.

The run loop tweaks are extremely conservative now - Since r503112 they are only enabled in 3 very specific places.

The repro steps don't involve menus, so I think it's unlikely that these are related.

I also could not repro. To move on these, we need a sample or crash report.

Note if AwSnap is appearing, it could be that the item you're trying to print is very complex, and consuming all the available memory. This could cause the problems described.

- If you type chrome://crashes/ into the location bar, are there any Crash Report IDs listed?
- When the print dialog "freezes", do you get a "beachball" mouse cursor?
- Are you able to close the dialog? (Is Chrome responsive after that?)

When it freezes, can you collect a sample? To do this, wait for the freeze to occur, then open `Activity Monitor` from Applications. Double-click the item with process name "Google Chrome" and click the "Sample" button in the bottom left. Then please save the result and attach to this bug.

Thanks!

Deleted: Screen Shot 2018-01-09 at 11.28.22 am.png 56.7 KB

	Screen Shot 2018-01-09 at 11.28.22 am.png 56.7 KB View Download

I have a ~10 year old mac mini sitting at my desk for working on this bug. I just haven't had time to get to it. There are a couple duplicates of this filed already.

I'm thinking of  bug 728075  and bug 774237.

Looks like we've had issues reproing this issue and have not been able to for quite some time. Due to the inactivity on this issue, I'm going to close this for now. Feel free to reopen or file a new issue if this repros in current versions of Chrome.