Adding Attachment to Gmail Web Client Crashes Browser
-
I have a client trying to send attachments from the Gmail web access. When the window to select files opens, sometimes she can attach a file, however most times it crashes the browser. This occurs in both Firefox and Chrome (default browser); it occurs with all file types (both sometimes attaching and usually crashing).
Windows Updates are current as are both browsers.
Is there some setting I should be looking for? For what it's worth, this crashing business does not occur on my Gmail accounts.
-
How big are the attachments? I'm not sure what it is, but there is a file size limit (but I've never seen it crash from that).
-
Check and make sure the file path that it is trying to open is accessible to your account. I've seen this happen a few times where my file-open dialog was trying to go to a network path and I hadn't connected up to it again since my last reboot.
-
@Scott said in Adding Attachment to Gmail Web Client Crashes Browser:
Is there some setting I should be looking for? For what it's worth, this crashing business does not occur on my Gmail accounts.
Your account, on their browsers?
-
Thank you for the quick replies.
The attachments aren't large, mostly around 100KB, some a few MB.
These files are located on user's Desktop. (Sometimes the given file will attach, other times the same file causes a crash)
No attachment problems using my Gmail both on their PC as well as my PCs.
-
@Scott said in Adding Attachment to Gmail Web Client Crashes Browser:
No attachment problems using my Gmail both on their PC as well as my PCs.
that is seriously weird, then.
-
Is the client's machine old / underpowered? Chrome can be a RAM hog, maybe the file attach window puts it over the tipping point.
-
Machine not old. AMD Ryzen 3, 8GB RAM.
Using it largely with Gmail, Google docs and such.
-
@RojoLoco said in Adding Attachment to Gmail Web Client Crashes Browser:
Is the client's machine old / underpowered? Chrome can be a RAM hog, maybe the file attach window puts it over the tipping point.
Appears that it must be account related, not machine related.
-
Reset the cache on both browsers.