Hmmm... I have no problems with chat on Ubuntu 14.04 LTS and FF 40.0.3 (opened 10 chat tabs, wrote some long messages, left them running for 30 minutes). I will test it on Windows and OSX. This is very weird and I don't know what could be the cause for now - it should be possible to debug if we reproduce the crash and locally revert changes that were made on and before 25.08. Please be patient. :)

If you have any problems with chat, just ping me on chat... :D Just kidding.

Thanks for the information. I've tested it on Windows XP (FF 30, 33, 40.0.3) on Virtualbox and it's fine but I'll make tests on real windows machine when I'll be at GOG.

We've made tests on Windows 8.1 with FF 35, 40.0.2, 40.0.3 - no signs of crash after many tabs opened for hours, sending messages etc. I don't say that it's not an issue, but we need to reproduce it to fix it.

What OS/browser/addons are you guys using?

If anyone encounter this, please list your browser addons, because we cannot reproduce the issue. I sam one list at the seventh page, but it would be really helpful if you all could list yours.

Open the Firefox menu, click Add-ons, and select Plugins. If you want to help more - try disabling all of your addons and tell us if this caused FF not to crash.

Then we will know if this is good trail.

This is what our QA tested:

- Virtual Machine with Windows 10, FF 40.0.3, multiple tabs open. Nothing.
- Virtual Machine with Windows 10, FF 40.0.3, single tab open. Nothing.
- Laptop with Windows 10, FF 40.0.3, multiple tabs open. Nothing.
- QA PC with Windows 8.1, FF 40.0.3, multiple tabs open. Nothing.
- QA PC with Windows 8.1, FF 40.0.3, multiple tabs open, some addons installed. Nothing.
- Samsung laptop with Windows 8.1, FF 35, 40.0.2, 40.0.3. Nothing.
- OS X 10.10 with FF 40.0.3, multiple tabs open, with some addons. Nothing.
- Ubuntu 14.04 LTS and FF 40.0.3. Nothing.
- Virtualbox Windows XP, FF 30, 33, 40.0.3. Nothing.


Pinging (not all of you reporting are here, sorry):

Thanks guys, that gives us new light on this bug. I didn't connect this with auto-expanding chat input before - I implemented it long ago and nobody reported crashes. I see there was a change in FF 40.0.0 connected to hardware vsync usage and scrolling released on August 11, 2015.

As we are detecting if scrollbar appears and instantly expanding input thereby removing the scrollbar - it could be connected, we will check this.

Still, we need to reproduce this to make tests and fix it. Please be patient. :)

P.S. I highly recommend Chrome or Chrome non-spying forks.

We couldn't reproduce it in any possible way on various machines... Maybe it's just bad luck that it's not crashing for us. ;P We already put a lot of effort into that, but we had different work to do (you'll see soon). I will check it also on my private win7 machine. Actually I have two, so keep fingers crossed that it will crash. :) We need to have that machine in our network.

Also, if any of you want to - maybe you could record a video (even with your phone and upload to dropbox :P) of how the crash happens?

Edit: Ha! I have your T-rex in the quote.

Actually I did - on my private PC.

To all:
We did put a lot of work into reproducing this - I really can't believe we can't do it and it must be something stupid. Like Mozilla doing AB tests for users and serving different FF updates for "our" part of Europe. :P But that's like impossible.

I did read on FF bugtracker in one of your reports, that the bug is not appearing in coming (Nightly) version. I cannot test it because it's not crashing on any machine for me, but if you're willing to do this - please do. :)

I have also another idea to let you great users test something, and I've created a simple test - please go to chat using this link:
https://www.gog.com/account/chat?gogisthebest (not that I mean GOG is the best, but it is :P )
This will disable feature of auto-expanding message input. Please report to me if you had crashes using this link or not. :) Thanks!


mrkgnao:
There is a much higher percentage of windows users on GOG.com website. :) I suppose linux users use magog because they like such tools. (I am linux user myself)

Great! Thanks! I need more users to confirm this so we can propose a solution.

Thank you all, so we see it has nothing to do with auto-expanding input... If anyone want to try Firefox nightly build please follow this link: https://nightly.mozilla.org/.

Thank you guys for helping us! So for now we know that:
- For some users "special link" with auto-expanding input disabled did help - but for some users it did not - so no conclusion here.
- For one user Nightly build helped. We need more. :) Shame that we can't test it ourselves in GOG. :(

Playing games. :)

For testing purposes. :P

Thanks for the info! So nightly legends were true. ;)

To all that had the problem - please update Firefox and report if you have any more problems.

Apparently we had non-reproducable bug that disappeared. ;)

To more interested in problem origin:
In Firefox changelog I see nothing that could be related. Only trace is messagesChannel, but I bet it's not that, and they did fix something more. :) They described memory leaks etc. in security fixes, maybe that's it.