hello, could you go to the firefox menu ≡ > help ? > troubleshooting information, copy the contents of that page and paste them here into a reply on the forum? this might give us a clue what is going on...

philipp said

hello, could you go to the firefox menu ≡ > help ? > troubleshooting information, copy the contents of that page and paste them here into a reply on the forum? this might give us a clue what is going on...

Thank you for your reply here is the information,

http://paste2.org/WmFxKN47

ok thanks, this looks a lot like bug 1139430 (and you happen to use the same very new nvidia driver like the people posting their information in the bug report).

do you have a way of reproducing the issue reliably & quickly? if so, and if you are willing to invest a bit of time it would be of great help if you could narrow down the timeframe of when the problem first occurred in the development builds of firefox - this can be done by using the mozregression tool, which will look a bit technical at first sight, but we can guide you through the steps. it shouldn't be that difficult, but will require a bit of time:

• first you'd have to download and install (confirm all setup steps & click close once the process is completed) the the tool from http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe
• then open windows explorer and navigate to your C:-drive and then the mozilla-build folder. in there you'll find a file named start-l10n.bat - just double-click on that.
• in the black terminal window that opens, type in:
  easy_install mozregression & hit enter
• once this process is finished, enter:
  mozregression --good=2014-10-01 --bad=2014-12-01 --bits=32
  into the same window.
• now the process will automatically download browser builds from the time the error first occurred - just wait until a firefox "nightly" window opens and test if you can reproduce the bug there. then close the browser windows and enter good or bad into the terminal depending on if you got the error this time.
• this process will continue automatically until the exact date is found when the bug was first introduced into the browser - the window will then display a so called regression window and a pushlog. this is the critical piece of information we'd need, so developers can take over and start fixing what's going wrong... please copy and paste this section into the forum here or make a screenshot of it.
• you can then close the terminal window and delete the C:\mozilla-build folder again.

thanks again & please feel free to ask if anything is unclear...

See also:

• [/questions/1048972] turning off hardware acceleration fixed my image loading issue. is there another way around this?

philipp said

ok thanks, this looks a lot like bug 1139430 (and you happen to use the same very new nvidia driver like the people posting their information in the bug report). do you have a way of reproducing the issue reliably & quickly? if so, and if you are willing to invest a bit of time it would be of great help if you could narrow down the timeframe of when the problem first occurred in the development builds of firefox - this can be done by using the mozregression tool, which will look a bit technical at first sight, but we can guide you through the steps. it shouldn't be that difficult, but will require a bit of time:

• first you'd have to download and install (confirm all setup steps & click close once the process is completed) the the tool from http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe
• then open windows explorer and navigate to your C:-drive and then the mozilla-build folder. in there you'll find a file named start-l10n.bat - just double-click on that.
• in the black terminal window that opens, type in:
  easy_install mozregression & hit enter
• once this process is finished, enter:
  mozregression --good=2014-10-01 --bad=2014-12-01 --bits=32
  into the same window.
• now the process will automatically download browser builds from the time the error first occurred - just wait until a firefox "nightly" window opens and test if you can reproduce the bug there. then close the browser windows and enter good or bad into the terminal depending on if you got the error this time.
• this process will continue automatically until the exact date is found when the bug was first introduced into the browser - the window will then display a so called regression window and a pushlog. this is the critical piece of information we'd need, so developers can take over and start fixing what's going wrong... please copy and paste this section into the forum here or make a screenshot of it.
• you can then close the terminal window and delete the C:\mozilla-build folder again.

thanks again & please feel free to ask if anything is unclear...

Well I could not reproduce the issue in those builds, and I started to think it was fault of add-blocker plug in but after the test finished I disabled the add-blocker plugin in my FF and well for some time it was ok but just now when I wanted to write this post I saw this. But now I have two ideas first was those builds using gpu acceleration and second does firefox starts to have issues when I use multiple google websites ?? Because I do not know if google intended this but FF goes into coma when I use google products.

Now I will try to disable every addon and see where it goes. 

after testing, Sadly same issue

if the timespan in the mozregression tool was to narrow, then please try to run it with just this command:

mozregression --good=2014-10-01 --bits=32