<< Show all questions

Chrome crashes on print viewall

From Viewall, then Print, I get:

"Print is unavailable because the page you were trying to print has crashed."

Consistently.

I have tried disabling all extensions that are likely suspects, no joy.

Chrome 15.0.874.121 m
Vista Home

Asked by on Nov 21, 2011 - 00:18

on Nov 21, 2011 - 01:26

Hello Larry,

please tell me:
- Did you try to clear your browser cache?
- How long is the task list you'd like to print?
- Does this issue also occur when trying to print in a different browser?
- Does this issue also occur with a single project (or a "7 days") list in Chrome?
- Does the print preview appear and then you see the error message or does this happen even before the page is being generated?


Best regards,
David

on Nov 21, 2011 - 02:24



please tell me:

Thank you, David. ANSWERS BELOW...

- Did you try to clear your browser cache? YES NO DIFFERENCE

- How long is the task list you'd like to print?
ABOUT 4 PAGES A4

- Does this issue also occur when trying to print in a different browser?
NO! IE not a problem.

- Does this issue also occur with a single project (or a "7 days") list in Chrome?
NO! It doesn't

- Does the print preview appear and then you see the error message or does this happen even before the page is being generated?

A PAGE MOMENTARILY APPEARS (THAT LOOKS LIKE THE GENUINE INTENDED OUTPUT) INSTANTLY FOLLOWED BY THE PRINT MENU PAGE (has a GRAY LEFT COLUMN plus a PREVIEW column) -- of which the "preview" is blank except for the error message.

Does this point a finger?

on Nov 22, 2011 - 13:49

I see this problem also. I do see it on Chrome, sometimes, on pages other than Todoist.

By the way, for TODOIST, I want not stamp a question as "ANSWERED" if all you have done is ask the author of the problem an extra question, as in this case.

on Nov 23, 2011 - 04:52

Hello,

@Larry
unfortunately, I wasn't able to reproduce this issue even with tasks lists longer than 4 pages.

Please try to print (or just access the print view using Ctrl+P) some other pages (not originating from Todoist) using Chrome and let me know if you also experience this issue.

---

@Bruce
I'm sorry for the confusion. The "answered" image is being added automatically whenever a staff member responds to a thread. We will consider changing this or implement an additional "solved" mark.

Thank you for your feedback


Best regards,
David

on Nov 23, 2011 - 21:45

David,
I have found this behavior to be intermittent, and have since had some success. Reboot seems to help; perhaps this is a chrome memory overflow problem. I'm happy to leave it there for now - let's see if others experience the same.

I agree with Bruce. If you only have one flag it has to be "solved" meaning "case closed". If you can run to two flags, the middle one can't be "answered"; perhaps you mean "pending" or "in progress", or "under investigation"? [Answered is done-and-dusted past tense, whereas pending suggests an ongoing activity that's still alive in the present continuous].

This particular case doesn't properly fit any of the above, but I won't complain if you call is closed (for now...).