Thee Chicago Wolf [MVP] wrote on 18/11/2014 18:02:
Thee Chicago Wolf (MVP) wrote on 17/11/2014 02:33:
On Sun, 16 Nov 2014 23:22:32 +0100, Ray_Net
<tbrraymond.schmit...@tbrscarlet.be> wrote:
Thee Chicago Wolf (MVP) wrote, On 16/11/2014 20:29:
Thee Chicago Wolf (MVP) wrote, On 16/11/2014 00:31:
Thee Chicago Wolf (MVP) wrote, On 15/11/2014 17:15:
On Sat, 15 Nov 2014 16:55:01 +0100, Ray_Net
<tbrraymond.schmit...@tbrscarlet.be> wrote:
Thee Chicago Wolf (MVP) wrote, On 15/11/2014 14:30:
On Sat, 15 Nov 2014 11:34:42 +0100, Ray_Net
<tbrraymond.schmit...@tbrscarlet.be> wrote:
Thee Chicago Wolf (MVP) wrote, On 15/11/2014 03:13:
On Fri, 14 Nov 2014 23:43:03 +0100, Ray_Net
<tbrraymond.schmit...@tbrscarlet.be> wrote:
Thee Chicago Wolf (MVP) wrote, On 14/11/2014 14:47:
On Fri, 14 Nov 2014 14:36:04 +0100, Ray_Net
<tbrraymond.schmit...@tbrscarlet.be> wrote:
David E. Ross wrote, On 13/11/2014 22:19:
On 11/13/2014 1:00 PM, Ray_Net wrote:
David E. Ross wrote, On 13/11/2014 19:17:
On 11/13/2014 8:07 AM, Ray_Net wrote:
This is the second occurrence: bp-ced0a98a-fbae-4da7-974e-8554d2141113
The first was: bp-5e2bebbb-695b-49e4-96f4-bb2da2141105
Both of them points to bug
https://bugzilla.mozilla.org/show_bug.cgi?id=759749
With the Status: RESOLVED FIXED
But not for me :-) It's not resolved nor fixed.
What can i do to get the correction ? Because reading the text of the
bug 759749 is incomprehensible/abstruse for me.
Although supposedly fixed this past January, several users (not only
you) have reported crashes since then.
Yes, i have also readed that, but in what SM version this bug is
supposed be fixed ?
I have 2.26.1
It was supposed to be fixed with Gecko 29, which is what SeaMonkey
2.26.1 uses.
Apparently there was a problem with my server settings and my reply to
you never made it through so here's a re-post:
Some talk on Bugzilla suggested that Google actually changed something
but it has not been determined as true. But there are also these bugs:
https://bugzilla.mozilla.org/show_bug.cgi?id=1085203
https://bugzilla.mozilla.org/show_bug.cgi?id=1090338
My hunch is it's still related to OMTC.
Also, please type about:support into the
URL bar and past the Graphics section to your reply.
Here is the content:
Graphics
Adapter Description Mobile Intel(R) 4 Series Express Chipset Family
Adapter Drivers igdumdx32 igd10umd32
Adapter RAM Unknown
Device ID 0x2a42
Direct2D Enabled true
DirectWrite Enabled true (6.2.9200.16571)
Driver Date 10-15-2010
Driver Version 8.15.10.2226
GPU #2 Active false
GPU Accelerated Windows 3/3 Direct3D 10
Vendor ID 0x8086
WebGL Renderer Google Inc. -- ANGLE (Mobile Intel(R) 4 Series Express
Chipset Family Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote false
AzureCanvasBackend direct2d
AzureContentBackend direct2d
AzureFallbackCanvasBackend cairo
AzureSkiaAccelerated 0
So from this I can see you're trying to use 2008 hardware with a 2013
OS. That GMA X4500 is not validated to work with Win 8/8.1. I suspect
that if you upgrade to some newer version of SM down the road, you'll
experience more and worse issues due to the change to OMTC. Well, at
least until the remaining OMTC issues figured out. And the issues
affecting people are *primarily* driver related. People using outdated
hardware on OSes they were not meant to run. The hardware is just
showing age and limitations.
I never try something :-)
I did not have an 2013 OS ... You said that my hadware is not validated
to work with Win 8, but i am, from the beginning near may 2011.
My OS is Win 7 Pro SP1 and i will not upgrade to Win8.
In fact to tell me that i should change my pc to avoid problem with new
versions of SM ... :-( So i must stay with my 2.26.1 .... but you ask
further why i did not upgrade my SM.
Finally must i stay with 2.26.1 or must i upgrade ?
Odd. It shows DirectWrite Enabled true (6.2.9200.16571) which is a
WIn 8 file. If you're on Win 7 then it seems the guys in Redmond are
just culling Win 8 DLLs and using them in WIn 7. Oh well.
In any case, try updating the Intel video drivers to the last version
available for your VGA chip: 15.17.19.2869. It seems you are using
32-bit windows so try these and report back.
https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&FamilyId=39&ProductID=2991&ProdId=2991
Thanks for your precise answer/counsel ...but reading this:
These software drivers are generic versions and can be used for general
purposes. However, computer original equipment manufacturers (OEMs) may
have altered the features, incorporated customizations, or made other
changes to the software or software packaging they provide. To avoid any
potential installation incompatibilities on your OEM system, Intel
recommends that you check with your OEM and use the software provided by
your system manufacturer.
on the page: https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=22165
Make me reluctant to install a new driver, because my pc is a DELL
laptop with a pre-installed Windows.
Dell does not make the VGA driver, Intel does so no harm. I mange
about 1000+ Dells of various makes and models (960, 980, 7010). I
never use Dell's drivers, I only use Intel's. Dell is notorious for
*not* updating the drivers even when newer ones are release by Intel.
Dell does not modify the original Intel ones, they simply re-package
them with their own installers and might add annoyware to it.
So you think that i can go forward and installing this news driver safely ?
And if the new driver sent me to a BSOD .... what will be my next step ?
I am a little bit afraid.....
What about : Turning off hardware acceleration ?
If you want, download the drivers and hold onto them and first try
disabling hardware accel. Test before and after effects but I think
you'll find the performance hit will be high. I don't suspect any
issues with the updated Intel drivers but you can always do a Last
Known Good Configuration (pressing F8 before Windows boots) *or* you
can do a System Restore to the date it was last working. I know you
won't have problems. Intel drivers are pretty solid as far as
updating.
OK, I have upgraded my driver - but from DELL Support Site - all goes
well till now.
I have tested StreetView at the same place where the last crash occurred
- all goes well, but with the old version, i was also unable to
reproduce the crash.
Ok so that is good news. I does point to some new function or feature
on Google Street View that requires proper driver support. This is
also what some of the Mozilla devs suspected. If you could, you please
type about:crashes into the URL bar and paste the most recent crash
URL? What version of driver did it install from Dell? If it's mid or
later 2014, you can likely at least update to SM2.29.1 and get the
benefit of HTTP Caching V2. 2.29.1 is based on Firefox 32 which
doesn't have OMTC that is still buggy with older Intel VGA drivers.
This is the last crash url:
http://crash-stats.mozilla.com/report/index/bp-ced0a98a-fbae-4da7-974e-8554d2141113
when i was with the Driver 6.2.9200.16571
Dell support Site downloaded this installation program to install the
latest video driver:
Video_Driver_CR3WK_WN_8.15.10.2869_A15.EXE
Ok, i will install 2.29.1 in a few days.
Ok, the 2869 driver is as new as your hardware will ever see. I
*think* some people had issues with this driver due to OMTC but not as
bad as people on older VGA hardware. I have a slew of Optiplex 960s
with this driver and they are, so far, running ok on FF33.x which is
akin to SM 2.30. Still, you'll be safe on 2.29.1 and perhaps wait
until SM 2.32 is released so they have more time to work out the
remaining issues with OMTC. OMTC is nice when it works on well vetted
hardware that proper driver support. Good luck.
I am now with SM 2.29.1 ... and the StreetView is more slower than when
i was under 2.26.1.
You didn't disable HWA did you? I think when SM 2.31 is released
you'll be able to take advantage of OMTC.
No i didn't disable Hardware acceleration.
What is OMTC ? A SM option ?
Perhaps slower means less chance to have a crash :-) As with a car
riding at a high speed can cause an accident.
Likely because Google changed some code recently in StreetView. But
some good news, this bug
https://bugzilla.mozilla.org/show_bug.cgi?id=1085203 seems to have
fixed the issue. This fix will likely be in SM 2.31 along with a slew
of other OMTC fixes.
- Thee Chicago Wolf [MVP]
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
