Your Time:
Our Time:
← Back to discussions

Ahh Snap, Google Chrome ran out of memory

Need help with a different issue? Search the forums or open a new ticket.
Open a support ticket

This topic has 9 replies, 3 voices, and was last updated 9 years, 7 months ago by rolinb.

  • 2017-01-14 at 3:34 am
    Support Expired
    #18626
    rolinb
    Participant
    • Topics: 1
    • Replies: 6
    • Total posts: 7
    • Post count: 6

    Hello Support,

    Love the MusicPlay theme and so does my client. Although not being used as a “Music” site, the functionality is perfect for what my client needs. However, since installing it’s been crashing Chrome and I get “Ahh Snap, Google Chrome ran out of memory trying to load your webpage.” error message. I tried clearing browser cache, clearing WP cache, refreshing pages, rebooting my computer, but it keeps happening after a period of time on the site (both Admin & Frontend).

    The site is on a VPS with plenty of power & resources to run it. I’ve been building websites for over 20 years and never had this kind of an issue before. Would you mind having a look?

    2017-01-16 at 10:45 am
    #18629
    Anonymous
    Inactive
    • Topics: 0
    • Replies: 3227
    • Total posts: 3227
    • Post count: 0

    It’s very strange!!!
    Try the instructions in the link bellow and let me know if you still have problems. https://support.google.com/chrome/answer/95669?co=GENIE.Platform%3DDesktop&hl=en

    2017-01-18 at 5:43 am
    Support Expired
    #18687
    rolinb
    Participant
    • Topics: 1
    • Replies: 6
    • Total posts: 7
    • Post count: 6
    This reply has been marked as private.
    2017-01-18 at 11:35 am
    #18693
    Anonymous
    Inactive
    • Topics: 0
    • Replies: 3227
    • Total posts: 3227
    • Post count: 0

    I have cross checked and it is not our theme issue. It’s related to something google chrome issue. You can have a look at it https://www.google.com/search?q=aw%20snap%20error%20chrome&rct=j
    So many other people are also facing this type of issue and don’t know what it is causing.

    2017-01-19 at 8:32 am
    Support Expired
    #18716
    rolinb
    Participant
    • Topics: 1
    • Replies: 6
    • Total posts: 7
    • Post count: 6
    This reply has been marked as private.
    2017-01-19 at 5:31 pm
    #18725
    Anonymous
    Inactive
    • Topics: 0
    • Replies: 3227
    • Total posts: 3227
    • Post count: 0

    It’s an issue with your browser google chrome and it is working in mozilla firefox. I don’t know what might be the issue with your chrome.
    Kindly try the instructions in the link below and see. https://support.google.com/chrome/answer/95669?co=GENIE.Platform%3DDesktop&hl=en

    2017-01-19 at 11:00 pm
    Support Expired
    #18730
    rolinb
    Participant
    • Topics: 1
    • Replies: 6
    • Total posts: 7
    • Post count: 6

    It doesn’t work in any Chrome. I tried on several different computers and it happens to everyone who looks at it using Chrome.

    Did you get it to work in Chrome?

    2017-01-20 at 7:45 am
    Support Expired
    #18731
    rolinb
    Participant
    • Topics: 1
    • Replies: 6
    • Total posts: 7
    • Post count: 6

    Now Firefox crashed twice on MusicPlay Theme, the site is Crashing more and more frequently in Chrome and now Firefox. I just bought MusicPlay and installed earlier this month and the problems started immediately. I opened this ticket soon after discovering the problem and doing some diagnosing myself with zero success. Over 20 years of web development and I’ve never had this happen until the day I installed the MusicPlay theme. It only happens on MusicPlay, usually within just a few minutes. It’s crashed all Chrome Browsers on every system I’ve tried it on… 6 computers and 2 mobile devices. And looks like it crashed yours too.

    Please don’t send me another link to Chrome support, it only happens on 1 site, its likely to be the site causing the problem. I installed on a fresh version of WordPress supported by the theme and it’s on a VPS with plenty of resources. It’s not Chrome causing the problem, it’s MusicPlay causing Chrome to crash… and now Firefox.

    Can someone at support please help?

    2017-01-20 at 10:56 am
    #18738
    Fem
    Keymaster
    • Topics: 2
    • Replies: 5215
    • Total posts: 5217
    • Post count: 6003

    Do you have Skype? please add us in Skype for faster support.

    Regarding the issue, I found my theme doesn’t crash after testing. But after reading some articles on the internet regarding this chrome crash I found it to be Large MP3 files (6-10MB+, lengthy audio) have error decoding audio buffer. It might be a bug in Chrome’s Web Audio implementation. I’ve tried some files that are slightly less large (about 6MB) and there is no crash, I found this audio buffer issue after opening your site in Mozilla Console mode and found the following message in console area after few seconds of the site loading.

    An unknown error occurred while processing decodeAudioData.

    I think it’s not a Chrome’s Web Audio Buffering issue too as you said it happens in your firefox as well, but still not sure why it’s happening for such large files. Try disabling the Audio Player in the bottom once to see or upload the small size audio file and see.

    2017-01-29 at 3:50 am
    Support Expired
    #18940
    rolinb
    Participant
    • Topics: 1
    • Replies: 6
    • Total posts: 7
    • Post count: 6

    That was it, good job. I just sent you a Skype Request discuss another issue. I have to refresh Video & Home pages before they display properly.

    Home: http://mastermentornetwork.com/wordpress/
    On first visit to page, the Header image is covered by the section below it about 80% of the way up. You can only see a sliver of the header image unless I click refresh, then it displays fine.

    Video pages: http://mastermentornetwork.com/wordpress/video/vasayo-intro/
    In Chrome only, When any Video page is opened, the body is blank, no video. It displays perfect after a quick refresh of the page.

    Any ideas?

You must be logged in to reply to this topic.