User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15 Build ID: 20130105222038 Steps to reproduce: Nothing in particular, just run Seamonkey Actual results: The hardware acceleration feature in Seamonkey 2.15 made Seamonkey crash consistently in just seconds after startup. It even made the Intel graphics driver crash, although the driver recovered. I'm using a Clevo P170EM notebook with Windows 7 64 bit. The notebook has the standard embedded Intel HD4000 graphics as well as a Nvidia GTX 675M graphics card. I'm using the latest Intel driver and the latest Nvidia driver (310.90). As far as I'm aware the Nvidia driver takes care of switching between the Intel graphics and the Nvidia graphics. If no high performance graphics are needed, the Intel graphics are used to save power. I started Seamonkey in save mode, then it worked fine, found some information about hardware acceleration, switched it off, restarted Seamonkey in normal mode, and everything worked fine.

Does the same thing happen for you in Firefox 18.0 ? Did you get & submit the crash reports (about:crashes)? Could you post the URLs.

Might this apply to you? Bug 828184 - startup crash in nsPrefBranch::GetIntPref with QIPCAP.dll (Websense Endpoint)

All crashes from 2013-01-17 and 2013-01-18 have to do with this problem.

There are 2 flash hangs in the reports but the other are crashes of the intel driver. That is a bug in the driver since the driver crashes. example ID from the reporter: bp-14bae504-e9e0-44c1-bf53-4f2ca2130117 FYI: I have on my laptop (from about:support in Seamonkey) : Adapter Description Intel(R) HD Graphics 4000 Driver Date 3-26-2012 Driver Version 8.15.10.2712 Adapter Description (GPU #2) NVIDIA GeForce GT 630M Driver Date (GPU #2) 5-28-2012 Driver Version(GPU #2)8.17.12.9687 I don't get any crashes of the driver at all.

The crash reports dated 2013-01-18 are actually older crashes (check the date of the crash), and are not related to this problem. I have no idea why they were reported on 2013-01-18. I once saw the graphics driver crash. The screen went black, and when it reappeared I got a small pop-up window explaining that the driver had crashed, but had recovered. This is the graphics information from my notebook: Adapter Description: Intel(R) HD Graphics 4000 Adapter Description (GPU #2): NVIDIA GeForce GTX 675M Adapter Drivers: igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32 Adapter Drivers (GPU #2): nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um Adapter RAM: Unknown Adapter RAM (GPU #2): 2048 ClearType Parameters: Gamma: 2200 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 50 Device ID: 0x0166 Device ID (GPU #2): 0x1212 Direct2D Enabled: no information DirectWrite Enabled: false (6.1.7601.17789) Driver Date: 12-12-2012 Driver Date (GPU #2): 12-29-2012 Driver Version: 9.17.10.2932 Driver Version (GPU #2): 9.18.13.1090 GPU #2 Active: false GPU Accelerated Windows: 0/3 Basic no information Vendor ID: 0x8086 Vendor ID (GPU #2): 0x10de WebGL Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics 4000) AzureCanvasBackend: cairo AzureContentBackend: none AzureFallbackCanvasBackend: none

There are basically 3 graphic card crashes. a) The usermode part of the driver crashes. In that case the application that used the windows API which itself called the driver will crash and in this case it's Seamonkey. This are your crash reports. b) The whole graphic card driver hangs and Windows restarts it. You get a notification. I don't know if this includes the kernel-mode part of the driver. c) the kernel-mode part of the driver crashes and you get a permanent black screen, a windows freeze, reboot or BSOD

I installed the Intel driver several weeks ago, and I had no problems. It was only after I installed the new Nvidia driver that the problems began. There is a Nvidia mechanism that decides which graphics engine to use, the Intel or the Nvidia depending on how much performance is needed. It is my guess that three is a problem between Seamonkey and hat mechanism, does that make sense?

i think this might be related to bug 829508 which also occurs in firefox.

I installed the Intel drivers at 2013-01-05, and had no problems. I installed the Nvidia drivers at 2013-01-17, and immediately afterwards the problems began. That can't be a coincidence can it?

Try to disable NVIDIA 3D Vision plugins.

(In reply to Scoobidiver (away) from comment #10) > Try to disable NVIDIA 3D Vision plugins. Dirk, do you still see this problem when using a current version?

No, not the Nvidia driver, but sometimes the Intel graphics driver crashes. There is definitely a big problem with the video in Seamonkey, or maybe just on configurations like this with two video adapters. All the time the browser window may become unresponsive, and then the mail window appears in front of the browser. You will also see a small blue revolving circle on the screen. When I have many tabs open, Seamonkey will become very sluggish. It has nothing to do with the amount of RAM, my notebook has 32GB, and usually I have at least 20GB free. I surely wish for a 64 bit Seamonkey, I think it will resolve these problems.

I would like to rectify my previous comments. I installed and ran MalwareBytes on my laptop, and it found some 90 problems, mostly related to two or three malware programs. After removing this junk I found that SeaMonkey was behaving again like it should, and much snappier. Most likely one of these programs intercepted all browser traffic, including the mail traffic since the mail agent is also part of the browser. That will also explain why the mail window popped up all the time.

From Comment 13 I suppose that problem is gone? If not, please reopen this bug and provide Crash IDs for latest crashes

I noticed the problem seems to have something to do with "browserhelper". In my user directory in Appdata/local there is a directory called Browserhelper. It contains a file called Browserhelper.txt. This file contains a link. When I close down Seamonkey, I can remove the directory and the file. After I restart Seamonkey, it will be much snappier, and the mail window will not suddenly pop-up any more. However after a while the directory and the file appear again. Malwarebytes regards this as malware. I have no idea what the link does, I copied the link in a browser tab and saw "ok".

Dirk can you still reproduce this? If so please provide a crash report ID from about:crashes. I checked our crash-stats data and there was only one report recently from a user who's on a very outdated driver (there's is March 23, 2013 while the latest for their device is September 24, 2014).

The problem was cause by some piece of **** called YTdownloader, after removing it, the problems were gone. However I'm experiencing similar problems now, in fact Seamonkey has become almost unusable. I'm running 2.40 64 bit now. Typing is almost impossible, scrolling too. All the time the screen freezes, that small blue activity circle appears, the small "X" box in the right upper corner of the windows turns red for a second or so, the window 'fades' for a few seconds, it is a disaster. I wish there would be something to check what SEamonkey is doing!!

(In reply to Dirk Munk from comment #17) > However I'm experiencing similar problems now, in fact Seamonkey has become > almost unusable. I'm running 2.40 64 bit now. Where did you download it, as only 32 bit versions are official, and despite 2.40 tagged as release, it wasn't released yet?

Yes, I know. But I usually have many tabs open, and the 32 bit version had problems with that. It often crashed. When I changed from 32 to 64 bit (with 2.37) the problems were gone and Seamonkey was much snappier. Since Windows 7, 64 bit is the standard for Windows, and in my very personal opinion Seamonkey should have had an official 64 bit version years ago. And I do know about plugins etc, but never the less. My version can be found here: https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/ I had no problems with the 64 bit version, until the present problems suddenly appeared in 2.39. I hoped 2.40 would resolve it, but alas......

Try this build and tell if it have the same problem - http://www.cs.iptcom.net/tmp/seamonkey-2.39.en-US.win64.installer.exe

I tried. At first it was a bit better, but soon it became as bad as before. When I'm typing in a Seamonkey window, keystrokes may end up in different Seamonkey windows, and even execute commands there! There is something badly wrong with the memory management.