It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hey, been using GOG for sometime now and as of last night I can not access the frontage of GOG using firefox. The second I hit enter firefox crashes. I was using version 32.0.3 but just updated to version 33 and still have the same problem.

I can access the rest of the site without issue and I can access the front page using chrome although it runs slower than normal. Haven't seen any posts on the forums from anyone else so I was wondering if anyone else is experiencing the same problem?
Using Firefox 33 on Win8 and having no issues with the GoG.com main page. Do you have any addons? Try disabling all extensions and re-enabling them one by one.
Firefox 33 on Win 7 and no problems here.
Just tried starting in safe mode and still crashes, I haven't made any changes to firefox in quite some time now
Works for me with both Firefox 33 on Win8 and Firefox 32 on Mint 17.
I have FF 32.0.1 with XP and the homepage works normally.
In mac on Firefox 33.0 I get

"A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue.

Script: [url=http://www.gog.com/js/a29a99b-b86a378.js:10]http://www.gog.com/js/a29a99b-b86a378.js:10[/url]"

Stopping the script works just fine and I haven't seen what it affects yet.

If you have made GOG your homepage or have it going to the page automatically at start up try closing it and going manually. Check if it pops up an unresponsive script warning such as above. If not see if you need to reset the warning.
Post edited October 17, 2014 by WhoKnowscs
Hmm, Well firefox crashes as it enters the site so I cant get any console logs from it, but it jumps to 12% cpu usage when it crashes as opposed to its regular 0.02% usage.
When I now try to go to my games library It loads very slowly.

On chrome theres no problematic outputs, will try on OSX later on tonight and see what happens.

Currently running on

Win 7 Ultimate x64
i7 quad-core
16GB ram


-------Edit-------

Think I've somewhat figured it out. Just tested it on waterfox and the front page loads but then crashes a few seconds later, so I created an new firefox profile and loaded with that and GOG loads without issue so it seems as though there's a corruption somewhere in the default profile even though Ive cleared my cache a few times :/
Post edited October 17, 2014 by Chriss316
Well, that was interesting. I've been getting this issue too for the last few weeks on my default firefox profile. I've been chalking it up to file cache corruption as I had a nasty freeze in windows around that time (corrupting my paging file). Since my firefox is heavily modded I keep chrome around for when pages go bad, and had been putting off fixing this; but your post got me wondering.

After clearing my cache I still was getting the crashes, so I disabled all my addons and the site worked. I then enabled/disabled my addons in halves until I found the troublesome addon.

Turns out it was NoSquint. I have a default text zoom of 120% (not full page zoom), and gog.com will crash at that level. I did some further testing and it looks like text zoom at 115% onwards will cause crashes. Full page zoom is fine. So if you are using NoSquint with text zooms apparently that can cause crashes.
avatar
lionicsheriff: Well, that was interesting. I've been getting this issue too for the last few weeks on my default firefox profile. I've been chalking it up to file cache corruption as I had a nasty freeze in windows around that time (corrupting my paging file). Since my firefox is heavily modded I keep chrome around for when pages go bad, and had been putting off fixing this; but your post got me wondering.

After clearing my cache I still was getting the crashes, so I disabled all my addons and the site worked. I then enabled/disabled my addons in halves until I found the troublesome addon.

Turns out it was NoSquint. I have a default text zoom of 120% (not full page zoom), and gog.com will crash at that level. I did some further testing and it looks like text zoom at 115% onwards will cause crashes. Full page zoom is fine. So if you are using NoSquint with text zooms apparently that can cause crashes.
Installed NoSquint on a fresh FF profile and it seems to be working fine for me at 115%+ (Forgot it existed, going to be keeping it now as im constantly squinting at my screen as my TV dosnt like using computers :p).

As for my default profile Ive tried clearing cookies and cache multiple times and starting in safe mode and it just flat out refuses to open the front page. Seems I may just have to use a new profile and start importing all my settings
Post edited October 18, 2014 by Chriss316
avatar
Chriss316: Installed NoSquint on a fresh FF profile and it seems to be working fine for me at 115%+ (Forgot it existed, going to be keeping it now as im constantly squinting at my screen as my TV dosnt like using computers :p).

As for my default profile Ive tried clearing cookies and cache multiple times and starting in safe mode and it just flat out refuses to open the front page. Seems I may just have to use a new profile and start importing all my settings
Just tested a blank profile myself, and it didn't crash. Reinstalling nosquint in default didn't work, but resetting all nosquint prefs in about:config did. I can now browse gog.com in glorious 120% :)

Edit: Nope spoke too soon. gog.com still had the default 120% *page* zoom. When I switched it over to *text* zoom I got crashes again.

Edit 2: in fact in the blank profile at 120% text zoom definitely causes firefox to become non responsive. Unlike my default profile though it will recover telling me that this script is busy [url=http://www.gog.com/js/a29a99b-b86a378.js:10]http://www.gog.com/js/a29a99b-b86a378.js:10[/url].
Post edited October 18, 2014 by lionicsheriff
You could try manually deleting the cache yourself, it is probably located in C:\Users\<username>\AppData\Local\Mozilla\Firefox\Profiles . See about:cache .
avatar
lionicsheriff: Just tested a blank profile myself, and it didn't crash. Reinstalling nosquint in default didn't work, but resetting all nosquint prefs in about:config did. I can now browse gog.com in glorious 120% :)

Edit: Nope spoke too soon. gog.com still had the default 120% *page* zoom. When I switched it over to *text* zoom I got crashes again.

Edit 2: in fact in the blank profile at 120% text zoom definitely causes firefox to become non responsive. Unlike my default profile though it will recover telling me that this script is busy [url=http://www.gog.com/js/a29a99b-b86a378.js:10]http://www.gog.com/js/a29a99b-b86a378.js:10[/url].
Realized I was testing with page zoom, so your right, on a fresh profile text zoom at 115%+ does crash FF

avatar
lionicsheriff: You could try manually deleting the cache yourself, it is probably located in C:\Users\<username>\AppData\Local\Mozilla\Firefox\Profiles . See about:cache .
Tried this earlier and it put FF into a crash loop as it kept trying to recover the last url upon opening.

Finally managed to get 1 crash report and it seems to be a plug in that's causing the crash with an exception_access_violation_read. Not sure why a fresh profile fixes the issue though as the plugins don't change with new profiles. If its an issue with my silverlight being out of date I'll probably just live with the new profile, I always find silverlight updates to be as inconvenient as flash updates :p
You can always try to reset your firefox profile. History, bookmarks and preferences will be kept, addons have to be reistalled afterwards, though.
Loosely translated, as i dont have the english version: Go to help -> Troubleshooting information
On the now opened webpage click "Reset Firefox"

After resetting just enable one addon after another and see if the page loads or not.
avatar
hohiro: You can always try to reset your firefox profile. History, bookmarks and preferences will be kept, addons have to be reistalled afterwards, though.
Loosely translated, as i dont have the english version: Go to help -> Troubleshooting information
On the now opened webpage click "Reset Firefox"

After resetting just enable one addon after another and see if the page loads or not.
Awesome that fixed it :D
Been using FF for years and never knew there was a reset option :p