Closed Bug 453869 Opened 17 years ago Closed 17 years ago

EXCEPTION_ACCESS_VIOLATION

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
Windows Vista
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: digitalxero, Unassigned)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.2.149.27 Safari/525.13 Build Identifier: Nightly Build 1220615848 (ftp://ftp.mozilla.org/pub/firefox/tinderbox-builds/mozilla-central-win32/1220615848/) The SunSpider js benchmark system crashes Minefield with the following crash report http://crash-stats.mozilla.com/report/index/94aeda97-7a06-11dd-9c3c-001a4bd43ed6?p=1 This happens immediately after clicking the start now link. Bug #453580 was reported as fixed for an earlier nightly build with a similar, but not identical crash report Reproducible: Always Steps to Reproduce: 1. Goto http://www2.webkit.org/perf/sunspider-0.9/sunspider.html 2. Click the Start Now link 3. Boom it dies. Actual Results: Browser Crash Expected Results: Results of the Benchmark test Since this is working for some people, I suspect it may be specific to AMD Quad Core CPU's about:buildconfig Build platform target i686-pc-mingw32 Build tools Compiler Version Compiler flags cl 14.00.50727.762 -TC -nologo -W3 -Gy -Fd$(PDBFILE) cl 14.00.50727.762 -GR- -TP -nologo -Zc:wchar_t- -W3 -Gy -Fd$(PDBFILE) Configure arguments --enable-application=browser --enable-update-channel=nightly --enable-update-packaging --enable-jemalloc
WFM in Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b1pre) Gecko/20080905031348 Minefield/3.1b1pre. Have you tried this in safe Mode? What Minefield build are you using, as 1220615848 is not the most recent.
Ok, tested this in safemode with nothing checked and it works fine
If it work in Safe Mode, it is a problem with an extension. Disable them one by one, then contact the author of the extension.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Clarify, disable till you find the problem one, contact the author of that one.
lol, ok found the plugin that was causing the issue. Google Update 1.2.131.11 which installed itself when I installed Chrome. So off to Google to bitch about their buggy plugin, though they will just blame it on a unstable build of FF
Dj: we shouldn't crash if that plugin is a Firefox add-on, with no native code (if it's a plugin like Flash, with native code, then it can crash us without our having a good story yet for stopping it -- Chrome has process isolation to help here, and we have long wanted that for plugins if not add-ons [both really], so we will work on this). I want to make sure a bug isn't being mis-blamed on Google here. Can someone point me to the Google Update 1.2.131.11 "plugin" download or source site? Thanks, /be
It seems to just be added to Firefox when Chrome is installed. i can look for it later though.
It's a plugin like flash, and the only way I know how to get it is to install Chrome from http://www.google.com/chrome It installs the Google Update Plugin which allows google to execute it's installer without prompting the user.
http://www.google.com/support/pack/bin/answer.py?hl=en&answer=30252 is the only info I could find on it. It seems to have been an old Google Labs experiment, then was bundled with Pack.
FYI, I created a bug for this in chromium: http://code.google.com/p/chromium/issues/detail?id=1585
You need to log in before you can comment on or make changes to this bug.