Introducting Grafx Bot
One of the new features of Firefox 4 is graphics hardware acceleration. This, along with the new layers code, will help improve Firefox performance during things like page rendering and full-screen video.
Firefox’s hardware acceleration interacts with a machine’s graphics hardware via DirectX or OpenGL, depending on platform. These interactions tend to be very sensitive to the graphics environment on the system (e.g., the specific video card(s) on the system, how much VRAM is available, the version of the video driver, the OS version, etc). In fact, there are so many permutations of the relevant factors that we can’t test them all internally. We need help from the community, so we can get exposure on as many unique hardware environments as possible.
To answer this need, I developed Grafx Bot. It’s an add-on that end users can download, which runs a suite of automatic tests on their machine that exercises interesting aspects of hardware acceleration. At the end of the tests, it allows users to post their results to Mozilla, where the data will be collected and analyzed, and hopefully lead to bug fixes and more reliable code for hardware acceleration than we’d otherwise have.
How it works
Grafx Bot is basically a new UI wrapped around Mozilla’s existing reftest framework. Reftest works by comparing the visual output of two different pages, which are supposed to be rendered identically. For example, this page and this page should be rendered identically, even though their markup is different. If reftest detects that the pages are rendered differently, it fails the test.
Grafx Bot runs a series of reftests that are designed to exercise the hardware acceleration code. Primarily, these are tests in the following categories: css-transitions, layers, ogg-video, scrolling, svg, text, text-decoration, and z-index. While the tests are executing, users will see images and colors flicker across their screen.
It’s possible that graphics hardware acceleration will produce small, but invisible changes in rendering between test pages. We don’t really care about these, we only care when the differences are visually apparent. Because of this, when Grafx Bot detects a reftest failure, it will ask the user if the differences are visible, by displaying both test images side-by-side.
Once the tests are complete, it will ask the user to click a button which submits the test results to Mozilla. After the data is in our database, the results will be reviewed, and bugs will be filed as needed.
I recommend that users install Grafx Bot in a clean profile with no other add-ons or extensions installed. This is because certain add-ons can interfere with Grafx Bot, or can cause it to run tests much slower than it would otherwise be able to. For instructions on how to create a new profile in Firefox, see this article at support.mozilla.org.
Types of acceleration tested
There are multiple types of hardware acceleration being developed. Here’s what Grafx Bot tests.
Grafx Bot runs the reftests with MOZ_ACCELERATED=11. This enables acceleration of layers via OpenGL (on Linux and Mac) and Direct3D (on Windows). On Windows, Grafx Bot also toggles Direct2D acceleration.
The latter type of acceleration can be toggled dynamically, whereas the former cannot. For this reason, on Windows only, Grafx Bot runs twice as many tests as on the other platforms. It basically runs each test twice, with different settings, like so:
- test 1a: test file with D2D enabled vs reference file with D2D enabled
- test 1b: test file with D2D enabled vs test file with D2D disabled
Test data
Along with the results of all the reftests that Grafx Bot performs, we collect anonymous hardware information. This allows us to associate test failures with specific hardware. Users can see the system information we collect before they submit test results by clicking on the “System info” link on Grafx Bot’s homepage. It looks something like this:
Even though this data is anonymous, this data is protected by Grafx Bot’s privacy policy (see link from the add-on’s homepage), and so is available only to Mozilla and to the user who submitted the test data.
Aggregate data, on the other hand, can be viewed by anyone. Click here to peruse Grafx Bot data summaries.
More info
Want more information on hardware acceleration features in Firefox? Check out these blog posts from Firefox graphics developers:
Firefox and Direct2d: performance analysis
Direct2d: hardware rendering a browser
I’ve installed and run the extension (on a nightly).
Now scrolling doesn’t work any more (big black screen instead of the page).
Does this extension reset everything how it was before?
paul
September 2, 2010 at 3:35 pm
just restarted. Sounds like it’s ok now. You don’t have to publish these two comments.
paul
September 2, 2010 at 3:41 pm
It appears there are some problems with D3D acceleration on Windows (which is enabled with MOZ_ACCELERATED=11), and these are likely responsible for the problems you saw. I’m going to turn this off in Grafx Bot, seems it doesn’t seem like it’s stable enough for testing during Firefox 4.0 Beta 5.
jagriffin
September 2, 2010 at 5:34 pm
I have the same problem with the latest nightly builds.
It is really annoying to restart firefox every time your screensaver goes on.
And even more it is annoying because after restart you have to blindly click on profile (i start without default profile to have a backup in case of bugs) because you see only black screen.
This is not even close to release. If such thing gets released then Firefox will die.
firefox user
September 10, 2010 at 7:06 pm
Do you see this problem only when using GrafxBot, or generally? Which version of GrafxBot are you running, and what’s your graphics hardware?
jagriffin
September 10, 2010 at 7:24 pm
It is generally. I found out about grafx box only by searching the web about Firefox 4 black screen bug.
Mozilla/5.0 (Windows NT 5.1; rv:2.0b6pre) Gecko/20100910 Firefox/4.0b6pre
firefox user
September 11, 2010 at 9:16 am
I get this issue as soon layers.accelerate-all is turned on. In general FF seems to be slower with hardware acceleration turned on.
Can anyone give hints on this issue. Links to the Bug, etc. Are there more bugs on this then 590328?
Morty
September 22, 2010 at 9:48 am
layers.accelerate-all may turn on acceleration which isn’t completely working in 4.0b6…you should try again when 4.0b7 comes out.
jagriffin
September 22, 2010 at 10:24 am
I’ve discovered an extra setting that will help some people turn on hardware acceleration… (it no longer works on my GeForce 6800 GT….
gfx.direct2d.force-enabled=true
After I’d set this and restarted FF 4, I got hardware acceleration!
It was slower than it used to be… but it was there again!
SarahC
December 10, 2010 at 10:13 pm
Just installed the prebeta 5 localised version and it looks good again.
firefox user
September 11, 2010 at 11:21 am
[...] us to improve hardware acceleration in Firefox: Install the Grafx Bot extension (details here and add-on [...]
Firefox 4 Beta: Latest update is here — what’s in it for web developers? ✩ Mozilla Hacks – the Web developer blog
September 7, 2010 at 9:05 pm
[...] This post was mentioned on Twitter by saneyuki_s, Mikko Ohtamaa. Mikko Ohtamaa said: Please help to collect hardware acceleration test data for Firefox 4: http://jagriffin.wordpress.com/2010/08/30/introducting-grafx-bot/ [...]
Tweets that mention Introducting Grafx Bot « JGriffin's Blog -- Topsy.com
September 8, 2010 at 2:30 am
I installed and ran it (ATI R300 chip on Kubuntu 10.04 Lucid Lynx). I ground through dozens of reftest “failures” that look pretty similar, many of them are just big green rectangles. Some feedback on this part:
On my 1280×1024 screen, the “Compare Test Results” window displays the two test visuals scaled down to fit, so I get subtle resize artifacts on the edges of colored squares unless I click both. The test canvas seems way bigger than it needs to be for all the tests I saw running.
Sometimes when I click to resize, the two visuals redisplay differently, e.g. the red rectangles on green go away. Odd.
It would be nice to have some feedback as to how many of these I have to click through.
Why are you asking me to compare two green rectangles? It seems some basic image analysis could tell you if they have the same pixel values or not.
Anyway, I’m happy to help. Cheers.
skierpage
September 8, 2010 at 3:01 am
When GrafxBot asks you to compare two green rectangles, it means that there are pixel differences between the two, but GrafxBot can’t tell if they are visually significant. So GrafxBot asks you to decide.
Good suggestion about telling users how many more comparisons are left. Thanks!
jagriffin
September 8, 2010 at 4:14 pm
Do the Grafx Bot tests take note of, and are they affected by, all the 3d and GL settings that have accumulated in about:config? I reset all the ones I could locate.
I spent time months ago fiddling with these to try and get Vladimir Vukićević’s Canvas 3D/WebGl demos working on my ATI r300 hardware, I never could (maybe lack of texture from FBOs or something in the ati_r300 drivers).
skierpage
September 8, 2010 at 3:11 am
Grafx Bot modifies these prefs during a test run: mozilla.widget.render-mode and gfx.font_rendering.directwrite.enabled. The value these prefs have before a test is run won’t affect the test, and the original values are restored at the end of the test.
Grafx Bot does not modify this pref: gfx.direct2d.disabled. You may get slightly different results depending on the value of this pref. A future rev of Grafx Bot will update this pref, as well as layers.accelerate-none and layers.accelerate-all.
jagriffin
September 8, 2010 at 4:38 pm
Grafx Bot Tests freezes here reliably at 102/759 test.
Mozilla/5.0 (X11; Linux x86_64; rv:2.0b4) Gecko/20100903 Fedora/4.0-0.6.b4.fc14 Firefox/4.0b4
akoubek:jetpack-sdk$ lspci |grep 00:02.0
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
jakoubek:jetpack-sdk$ lspci -n |grep 00:02.0
00:02.0 0300: 8086:2a42 (rev 07)
jakoubek:jetpack-sdk$
Matěj Cepl
September 8, 2010 at 7:37 am
Sorry to hear that. Can you try again with Firefox/4.0b5 and let me know if that still occurs?
jagriffin
September 8, 2010 at 4:13 pm
yes, progress! Now Firefox freezes on 104th test
Matěj Cepl
September 10, 2010 at 10:34 pm
[...] können aber helfen, Fehler in dem System zu finden. Dazu steht die Browsererweiterung Grafx Bot zur Verfügung. Video: Firefox 4 Beta 5 mit Hardwarebeschleunigung und Audio-API [...]
Beta 5: Firefox 4 mit Hardwarebeschleunigung und Audio-API
September 8, 2010 at 8:30 am
[...] this new feature and help out testing and improving it. The company posted a new extension called Grafx Bot that runs several tests and submits the results to Mozilla, if you agree. The goal is to evaluate [...]
More Firefox 4 Feature Freeze Delays? | ConceivablyTech
September 8, 2010 at 5:33 pm
Do you want us to rerun and submit new data for each FF release or each nightly?
Rob
September 8, 2010 at 9:14 pm
Each new beta release would be enough…thanks!
jagriffin
September 8, 2010 at 9:28 pm
Hi jagriffin,
Thanks for the testing plugin. I’m about to install and run it. Hopefully going back to my FF 3.6 wont cause any problems for normal running?
I wonder if you’d know why on some nightly builds, all the hardware acceleration is disabled, yet on the last beta 6 it works ok… does that mean the GFX card detection code’s still being worked on?
I get lost in the Mozilla update pages. o_O
SarahC
October 23, 2010 at 10:40 pm
Grafx Bot will disable itself on FF 3.6, so shouldn’t cause any problems.
I’m not sure why hardware acceleration would be disabled on some nightly builds.
jagriffin
October 24, 2010 at 4:08 pm
I installed the extension and restarted FF, whereupon it crashed on every start (I’ve submitted the report), so I’ve had to go back to FF3 to remove the extension…
Starting FF4 from a terminal with the extension installed produced
###!!! ABORT: X_GLXCreateContext: BadValue (integer parameter out of range for operation): file /builds/slave/linux_build/build/toolkit/xre/nsX11ErrorHandler.cpp, line 190
Mark
September 8, 2010 at 10:00 pm
Sorry to hear that Mark. Do you mind telling me what your DISPLAY environment variable is?
jagriffin
September 9, 2010 at 3:07 am
:0.0
Also: FF4.0b5, Fedora 13 64-bit, NVIDIA card & drivers with working hardware acceleration
Mark
September 9, 2010 at 8:41 pm
I ran the test right after I installed the addon. How do I run it a 2nd time?
thinsoldier
September 9, 2010 at 3:55 am
To run the test a second time, choose “Grafx Bot” from the tools menu. If you’re running Windows 7 and the tools menu isn’t visible, click the Firefox button, then click the right arrow next to the Options menu, and select Menu Bar.
jagriffin
September 9, 2010 at 4:48 pm
I ran FX4.0b5 on WinXP SP3 with Geforce3 Ti200, a D3D8, OpenGL 1.4 graphic card. When watching any html5 video with fullcreen, FX hogged almost cpu usage and got a jerky playback, which looks like stretching the video with cpu not gpu.
I know FX4 uses D3D9 to accelerate compositing operations on XP, but not sure whether D3D9 API calls to hardware stretching function of D3D8 card.
I guess cairo opengl backend may help this problem but can’t find any option to enable it on XP. Mplayer with opengl renderer works very well on my system(XP + geforce3).
larz
September 9, 2010 at 4:47 pm
D3D9 isn’t on by default in FF4.0b5, but it may be in FF4.0b6. You’ll be able to toggle it in FF4.0b6 by toggling the bool prefs layers.accelerate-all and layers.accelerate-none.
jagriffin
September 9, 2010 at 4:55 pm
I have completed the test and pressed the send button ,then the testing window disappeared immediately without any feedback messages.
Was it a normal situation? There is no recored about my graphic card in Grafx Bot data summaries.
larz
September 9, 2010 at 8:37 pm
Gets stuck at 2% (19/759) for quite a long time, then resumes. Just noting in case this might happen to others.
System Information
Display Vendor: Device (0×1002)
Display Adapter: Device 1002:5835
Display Chipset: 0×5835
Display RAM: 256 MB
Display Drivers: Mesa DRI R200 (RS300 5835) 20090101 AGP 4x x86/MMX/SSE2 TCL (Tungsten Graphics, Inc.)
Driver Version: 1.3 Mesa 7.8.2
Display Settings: 1280 x 800 x 24
OS: Arch Linux
vajorie
September 9, 2010 at 6:59 pm
When someone has problem with speed of rendering which is related to hardware acceleration what’s best to report? Is running Grafx Bot all what is needed or do you want to know some special info about hw configuration?
Pavel Cvrcek (Mozilla.cz)
September 9, 2010 at 8:01 pm
If you go to the links under “Previous test results” from the Grafx Bot start page, you’ll see the test results you submitted. One of the lines is “acceleration rate”. If this number is negative, Grafx Bot will flag it and we’ll know about it, and you don’t need to do anything else. If this number is positive, it means the problem was not detected by Grafx Bot, so you should feel free to file a bug in bugzilla, under component Core: Graphics. If you file a bug, please describe what scenarios rendering seems slow in, and what your graphics hardware is. Thanks.
jagriffin
September 9, 2010 at 8:47 pm
[...] je též citlivá na grafické karty a ovladače k nim. Z tohoto důvodu Mozilla vytvořila nástroj Grafx Bot, což je rozšíření pro Firefox, které pomůže otestovat vaši grafickou kartu a výsledky [...]
Linux Blog » Blog Archive » Pomozte otestovat hardwarovou akceleraci Firefoxu 4.0!
September 10, 2010 at 7:18 am
Is is useful if I run the tests on the occasional nightly build I download or is doing it one on Beta 5 enough data for someone’s specific hardware + OS setup?
voidmind
September 10, 2010 at 12:33 pm
It’s enough to run it once per beta, so if you could do it again on beta6, that would be great!
jagriffin
September 10, 2010 at 4:55 pm
I wanted to try it out on latest nightly (Mozilla/5.0 (Windows NT 6.0; rv:2.0b6pre) Gecko/20100913 Firefox/4.0b6pre), but nothing is happening at all. “Current test results” tab just shows “REFTEST INFO | Starting tests” and nothing else. I’m using clean install of newest nightly so all configuration should be default. Just in case, I’ll try once more with next version tomorrow.
opas
September 13, 2010 at 6:26 pm
After you start a test and nothing happens, could you look at the error console and see if any errors are reported?
jagriffin
September 14, 2010 at 5:53 pm
Me too, the test doesn’t strat, whether graphic acceleration is on or off.
Windows Xp
Firefox 4.0b7pre
Intel graphics (I don’t know if that’s related here)
Error console:
Error: __LOCATION__ is not defined
Source File: resource://grafxbot/grafxbot.jsm
Line: 57
Error: uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import]” nsresult: “0×80520012 (NS_ERROR_FILE_NOT_FOUND)” location: “JS frame :: chrome://grafxbot/content/test-driver.js :: gtd_submit :: line 199″ data: no]
bb
September 15, 2010 at 8:40 am
For me, it produces the errors:
Error: __LOCATION__ is not defined
Source File: resource://grafxbot/grafxbot.jsm
Line: 57
Error: uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import]” nsresult: “0×80520012 (NS_ERROR_FILE_NOT_FOUND)” location: “JS frame :: chrome://grafxbot/content/test-driver.js :: gtd_submit :: line 199″ data: no]
Mozilla/5.0 (Windows NT 5.1; rv:2.0b7pre) Gecko/20100915 Firefox/4.0b7pre
Intel graphics.
flying fox
September 15, 2010 at 4:21 pm
Grafx Bot seems to have stopped working for me. Messages in the Error Console of my Fx 4.0b7pre on Ubuntu:
—
Warning: Cannot load binary components from a jar.
Source File: grafxbot@mozilla.org.xpi:chrome.manifest
Line: 11
—
Error: __LOCATION__ is not defined
Source File: resource://grafxbot/grafxbot.jsm
Line: 57
—
Error: uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import]” nsresult: “0×80520012 (NS_ERROR_FILE_NOT_FOUND)” location: “JS frame :: chrome://grafxbot/content/browser-overlay.xul :: grafxBotHelperInit :: line 11″ data: no]
—
Been
September 15, 2010 at 4:45 pm
Yes, some rules were changed in FF4.0b7pre that broke GrafxBot; I’ll post a new version shortly which fixes this problem.
jagriffin
September 15, 2010 at 9:26 pm
Does not work for me either, clicking on start does nothing.
Error console shows:
Error: uncaught exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getBoolPref]” nsresult: “0x8000ffff (NS_ERROR_UNEXPECTED)” location: “JS frame :: chrome://grafxbot/content/test-driver.js :: gtd_submit :: line 167″ data: no]
Mozilla/5.0 (X11; Linux i686; rv:2.0b6) Gecko/20100101 Firefox/4.0b6
Bart
September 17, 2010 at 7:04 am
Błąd: uncaught exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getBoolPref]” nsresult: “0x8000ffff (NS_ERROR_UNEXPECTED)” location: “JS frame :: chrome://grafxbot/content/test-driver.js :: gtd_submit :: line 167″ data: no]
Ubuntu 10.04 FF 4.0 Beta 6
Display Drivers: GeForce 9600 GT/PCI/SSE2 (NVIDIA Corporation)
Driver Version: 3.3.0 NVIDIA 260.19.04
zil
September 17, 2010 at 7:16 am
In Peacekeeper benchmark with
layers.accelerate-all=true
i got worst score then with layers.accelerate-all=false
Why?
Also cant submit results because when
layers.accelerate-all=true
popup is empty (dont draw content) until i set it to false in about:config.
Test pilot popup box is white also save file and other.
Windows XP SP3
ff4
September 17, 2010 at 11:56 am
Just a couple of suggestions and questions:
1) Can you create a toggleable grid (maybe with small numbers that can be put in different quarters of the grid’s boxes) that can be overlayed over the compare results? That would make the comparison much easier.
2) Does running the test in the background make any difference? Or does the window always require top focus?
3) If displaying the image on top is critical, is it worth putting up a warning to people to not touch their machine while it is executing?
4) If displaying the image on top is critical, is it worth checking the delay of any screen lock / power saver to make sure it won’t conflict with the expected run of the test?
BarryM
September 17, 2010 at 2:49 pm
[...] And don’t forget to Install the Grafx Bot [...]
Firefox 4: recent changes in Firefox ✩ Mozilla Hacks – the Web developer blog
September 20, 2010 at 11:21 am
Linux Firefox Nighties stopped working. It shows the page, but I when I click on the “start the tests” button it doesn’t do anything.
Marc Harter
September 21, 2010 at 2:19 pm
Sorry about that, you can download 0.1.27, which fixes the Linux break, at https://addons.mozilla.org/en-US/firefox/addon/200733/versions/?page=1#version-0.1.27
jagriffin
September 21, 2010 at 5:41 pm
Works great, running it now!
Marc Harter
September 21, 2010 at 10:49 am
[...] 그리고 Grafx 봇을 꼭 설치해 주시길 [...]
파이어폭스4 : 파이어폭스에서 최근 바뀐 점 ✩ Mozilla 웹 기술 블로그
September 21, 2010 at 6:33 pm
I have been installed the release 0.1.27 that you pointed out. But the hardware acceleration does not work.
I’m using Linux 64bit with the stock Ubuntu Desktop 10.04.1 LTS (plus latest updates). My hardware is a Lenovo Thnkpad T500 laptop with just an Intel card GM45.
Once I clicked start on the grafx bot page, it is requesting to restart Firefox, so I did, but then when it is again started I only see the window border, the inner part is blank (background colour only). Though the page and menu are there, because the mouse arrow changes when hovering over the empty area.
By trial/error I manage to hit the start button, and the test started, I even got the result window (I know it only from the window title), but also for the 2 popup windows, the inner part of them were just blank.
So I could not give any feedback, because I did not find how to send it. But hardware acceleration obviously does not work on my platform.
Do you know of a proper place to give this feedback?
Huygens_25
September 22, 2010 at 12:16 pm
Thanks for trying it out. It would be great if you could file a bug report here: https://bugzilla.mozilla.org/enter_bug.cgi?product=Core
Use ‘Graphics’ as the component.
jagriffin
September 22, 2010 at 1:26 pm
After doing the test, 100% OK, I was a little surprised, to get no info in the processed report about how fast my graphic card was, or how many features had been accelerated.
Well if you ever have the opportunity to add this to the test, maybe through some comparative testing of the speed of the operations you run in the test with and without enabling acceleration ?
jmdesp
September 23, 2010 at 5:02 am
Tried running the test, seemed to be fine, one fail that showed two green boxes that looked identical, so I clicked Pass. The results window popped up, but the content of the window didn’t refresh at all, just showed a copy of the chrome://grafxbot/content/start-testing.html webpage behind it. The mouse turns to a text-entry cursor when I hover over parts of the window, so I know there should be something there, but I can’t submit the results cos I can’t see any buttons, or read anything. The window also doesn’t refresh if I move it around or offscreen either. Seems like a gfx card/driver issue. I’m running XP64, with an nVidia 7300GT (old card I know, but OK), with latest drivers, and not had any problems with the card before. Any ideas or known issues I’m not aware of?
Cheers
GaryB
September 25, 2010 at 7:12 pm
Please try running the test again once FF 4.0b7 comes out, and if you continue to see the problem, consider filing a bug in Bugzilla. Thanks!
jagriffin
September 27, 2010 at 9:54 am
I just downloaded this extension (also to see if hardware accel works on OS X
) but it gives me an error:
uncaught exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getBoolPref]” nsresult: “0x8000ffff (NS_ERROR_UNEXPECTED)” location: “JS frame :: chrome://grafxbot/content/test-driver.js :: gtd_submit :: line 167″ data: no]
Line 0
I am using the latest nightly (4.0b7pre). I saw you where working on a new version which should fix this error. Is there any information regarding this new version?
PatrickB
September 26, 2010 at 2:44 pm
Yes, please download the new version at https://addons.mozilla.org/en-US/firefox/addon/200733/versions/?page=1#version-0.1.27
It should resolve that problem.
jagriffin
September 27, 2010 at 9:53 am
Hello guy, i’m a fresh newb happy to discover more and more about the IT world, I’m on the regular beta not nightly but the test failed after i clic manually on fail. i got a regular graphic card an XP
drymr
October 1, 2010 at 1:42 am
when will Grafx Bot support SeaMonkey?
bmw
October 3, 2010 at 2:38 pm
We’re sorry, there was a problem while sending your test results to Mozilla. Please try again later!
Error details:
Unhandled Exception
Unhandled Exception
An unhandled exception was thrown by the application.
Jens
October 27, 2010 at 11:56 am
Sorry about that, there was a permissions problem in the db, should be fixed now.
jagriffin
October 27, 2010 at 1:44 pm
Test 105/797 (13%) never finishes. You can see a fully green page after some short fully-black flicker.
If you need more info, just ask.
Grafx Bot 0.1.27
$ firefox –version
Mozilla Firefox 4.0b8pre
$ uname -a
Linux cami 2.6.34-gentoo-r12 #1 SMP Sun Oct 31 10:18:50 CET 2010 x86_64 Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz GenuineIntel GNU/Linux
$ X -version
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.34-gentoo-r1 x86_64
Current Operating System: Linux cami 2.6.34-gentoo-r12 #1 SMP Sun Oct 31 10:18:50 CET 2010 x86_64
Kernel command line: root=/dev/sda3 noapic softlevel=default
Build Date: 20 August 2010 04:28:29AM
Current version of pixman: 0.18.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
$ /usr/sbin/lspci | grep VGA
05:00.0 VGA compatible controller: nVidia Corporation GT200b [GeForce GTX 275] (rev a1)
# grep -A5 glx /var/log/Xorg.0.log
(II) “glx” will be loaded. This was enabled by default and also specified in the config file.
(II) “record” will be loaded. This was enabled by default and also specified in the config file.
(II) “dri” will be loaded by default.
(II) “dri2″ will be loaded by default.
(II) LoadModule: “glx”
(II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
(II) Module glx: vendor=”NVIDIA Corporation”
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 195.36.31 Thu Jun 3 08:59:25 PDT 2010
(II) Loading extension GLX
(II) LoadModule: “extmod”
$ glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
server glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
GLX_EXT_swap_control, GLX_EXT_texture_from_pixmap, GLX_ARB_create_context,
GLX_ARB_create_context_profile, GLX_ARB_multisample, GLX_NV_float_buffer,
GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB
client glx vendor string: NVIDIA Corporation
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info,
GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync,
GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_ARB_create_context,
GLX_ARB_create_context_profile, GLX_NV_float_buffer,
GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float,
GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB,
GLX_NV_present_video, GLX_NV_copy_image, GLX_NV_multisample_coverage,
GLX_NV_video_capture
GLX version: 1.4
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
GLX_EXT_swap_control, GLX_EXT_texture_from_pixmap, GLX_ARB_create_context,
GLX_ARB_create_context_profile, GLX_ARB_multisample, GLX_NV_float_buffer,
GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB,
GLX_ARB_get_proc_address
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 275/PCI/SSE2
OpenGL version string: 3.2.0 NVIDIA 195.36.31
OpenGL shading language version string: 1.50 NVIDIA via Cg compiler
OpenGL extensions:
GL_ARB_color_buffer_float, GL_ARB_compatibility, GL_ARB_copy_buffer,
GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_depth_texture,
GL_ARB_draw_buffers, GL_ARB_draw_elements_base_vertex,
GL_ARB_draw_instanced, GL_ARB_fragment_coord_conventions,
GL_ARB_fragment_program, GL_ARB_fragment_program_shadow,
GL_ARB_fragment_shader, GL_ARB_framebuffer_object,
GL_ARB_framebuffer_sRGB, GL_ARB_geometry_shader4, GL_ARB_half_float_pixel,
GL_ARB_half_float_vertex, GL_ARB_imaging, GL_ARB_map_buffer_range,
GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query,
GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, GL_ARB_point_sprite,
GL_ARB_provoking_vertex, GL_ARB_seamless_cube_map, GL_ARB_shader_objects,
GL_ARB_shading_language_100, GL_ARB_shadow, GL_ARB_sync,
GL_ARB_texture_border_clamp, GL_ARB_texture_buffer_object,
GL_ARB_texture_compression, GL_ARB_texture_compression_rgtc,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar,
GL_ARB_texture_env_dot3, GL_ARB_texture_float,
GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample,
GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle,
GL_ARB_texture_rg, GL_ARB_transpose_matrix, GL_ARB_uniform_buffer_object,
GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object,
GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_vertex_shader,
GL_ARB_window_pos, GL_ATI_draw_buffers, GL_ATI_texture_float,
GL_ATI_texture_mirror_once, GL_S3_s3tc, GL_EXT_texture_env_add,
GL_EXT_abgr, GL_EXT_bgra, GL_EXT_bindable_uniform, GL_EXT_blend_color,
GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate,
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_compiled_vertex_array,
GL_EXT_Cg_shader, GL_EXT_depth_bounds_test, GL_EXT_direct_state_access,
GL_EXT_draw_buffers2, GL_EXT_draw_instanced, GL_EXT_draw_range_elements,
GL_EXT_fog_coord, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample,
GL_EXTX_framebuffer_mixed_formats, GL_EXT_framebuffer_object,
GL_EXT_framebuffer_sRGB, GL_EXT_geometry_shader4,
GL_EXT_gpu_program_parameters, GL_EXT_gpu_shader4,
GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil,
GL_EXT_packed_float, GL_EXT_packed_pixels, GL_EXT_pixel_buffer_object,
GL_EXT_point_parameters, GL_EXT_provoking_vertex, GL_EXT_rescale_normal,
GL_EXT_secondary_color, GL_EXT_separate_shader_objects,
GL_EXT_separate_specular_color, GL_EXT_shadow_funcs,
GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_texture3D,
GL_EXT_texture_array, GL_EXT_texture_buffer_object,
GL_EXT_texture_compression_latc, GL_EXT_texture_compression_rgtc,
GL_EXT_texture_compression_s3tc, GL_EXT_texture_cube_map,
GL_EXT_texture_edge_clamp, GL_EXT_texture_env_combine,
GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic,
GL_EXT_texture_integer, GL_EXT_texture_lod, GL_EXT_texture_lod_bias,
GL_EXT_texture_mirror_clamp, GL_EXT_texture_object,
GL_EXT_texture_shared_exponent, GL_EXT_texture_sRGB,
GL_EXT_texture_swizzle, GL_EXT_timer_query, GL_EXT_transform_feedback2,
GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, GL_IBM_rasterpos_clip,
GL_IBM_texture_mirrored_repeat, GL_KTX_buffer_region, GL_NV_blend_square,
GL_NV_conditional_render, GL_NV_copy_depth_to_color, GL_NV_copy_image,
GL_NV_depth_buffer_float, GL_NV_depth_clamp, GL_NV_explicit_multisample,
GL_NV_fence, GL_NV_float_buffer, GL_NV_fog_distance,
GL_NV_fragment_program, GL_NV_fragment_program_option,
GL_NV_fragment_program2, GL_NV_framebuffer_multisample_coverage,
GL_NV_geometry_shader4, GL_NV_gpu_program4, GL_NV_half_float,
GL_NV_light_max_exponent, GL_NV_multisample_coverage,
GL_NV_multisample_filter_hint, GL_NV_occlusion_query,
GL_NV_packed_depth_stencil, GL_NV_parameter_buffer_object,
GL_NV_parameter_buffer_object2, GL_NV_pixel_data_range,
GL_NV_point_sprite, GL_NV_primitive_restart, GL_NV_register_combiners,
GL_NV_register_combiners2, GL_NV_shader_buffer_load,
GL_NV_texgen_reflection, GL_NV_texture_barrier,
GL_NV_texture_compression_vtc, GL_NV_texture_env_combine4,
GL_NV_texture_expand_normal, GL_NV_texture_rectangle,
GL_NV_texture_shader, GL_NV_texture_shader2, GL_NV_texture_shader3,
GL_NV_transform_feedback, GL_NV_transform_feedback2,
GL_NV_vertex_array_range, GL_NV_vertex_array_range2,
GL_NV_vertex_buffer_unified_memory, GL_NV_vertex_program,
GL_NV_vertex_program1_1, GL_NV_vertex_program2,
GL_NV_vertex_program2_option, GL_NV_vertex_program3,
GL_NVX_conditional_render, GL_NVX_gpu_memory_info,
GL_SGIS_generate_mipmap, GL_SGIS_texture_lod, GL_SGIX_depth_texture,
GL_SGIX_shadow, GL_SUN_slice_accum
Carsten Milkau
November 7, 2010 at 5:48 am
My (portable) pc is a bi card Intel/ATI (Samsung R525) running with linux (ubuntu 10.10) and i just upgraded to Fx 4 b7… i installed the grafx bot to and…
when i scroll this very page, everything got mungled, artifacts scramble the layout…
Display Vendor: Device (0×1002)
Display Adapter: Device 1002:68e0
Display Chipset: 0x68E0
Display RAM: 256 MB
Display Drivers: ATI Mobility Radeon HD 5000 Series (ATI Technologies Inc.)
Driver Version: 4.0.10237 Compatibility Profile Context
Display Settings: 1366 x 768 x 24
Da Scritch
November 11, 2010 at 3:59 pm
I dont understand: 4 hours of sleeping later, (a restart and still on batteries), the browser seems okay again.
And this test http://demos.hacks.mozilla.org/openweb/HWACCEL/ , it went up from 5 FPS to 11…
Da Scritch
November 11, 2010 at 9:15 pm
hi, im trying to get this to run on my macbook pro, but i just get a blank white window. I don’t think acceleration of any kind is working at all in firefox.
Any ideas? I’d like to run it on my machine…
Details from grafx bot:
Display Vendor: NVIDIA (0x10DE)
Display Adapter: NVIDIA GeForce GT 330M
Display Chipset: 0x0A29
Display RAM: 256 MB
Display Drivers: N/A
Driver Version: N/A
Display Settings: 1680 x 1050 x 32
simon
December 10, 2010 at 3:21 pm
Which version of Firefox are you running?
jagriffin
December 10, 2010 at 4:21 pm
Grafx bot ? support ? (nighty/Minefield/64bit)
———————————————
their is no support for nighty / Minefield
and
no support for 64bit / Minefield
———————————————
? Bug ?
David
January 1, 2011 at 2:20 pm
There is no support for 64-bit Windows builds, since that build isn’t officially supported for Firefox 4. It should work with other 4.0b9pre nightlies, though, if you’re using GrafxBot 0.1.29. If you’re using that version and it doesn’t work, please send me some details about what’s going wrong. Thanks!
jagriffin
January 3, 2011 at 10:44 am
not compatible with… Minefield
David
January 4, 2011 at 4:00 pm
Graphx bot reports my VRAM as 256 MB while it actually is 512 MB.
ATI RADEON 4850, Ubuntu 10.10 64 bit with fglrx drivers version 10.12.
And in the stress test i get jkust 7 fps average.
rajeev
January 10, 2011 at 3:14 am
I am using Firefox 4 beta 9. On a new profile I installed GrafxBot, ran the tests and checked on ‘I agree to…’ and Submitted the results.
But the results are not going. It is stuck on :
Sending test results to Mozilla…
I re-tried by starting firefox again, re-running the tests, same problem.
Outspoken
January 15, 2011 at 6:57 am
What OS are you using, and what version of Grafx Bot?
jagriffin
January 15, 2011 at 11:16 am
I get the same error, although I don’t create a new profile. I’m using Windows 7 x64
JasonX
January 15, 2011 at 8:52 pm
GrafxBot is not compatible with 64-bit Windows right now, sorry.
jagriffin
January 18, 2011 at 11:12 am
I get the following error:
———————————-
We’re sorry, there was a problem while sending your test results to Mozilla. Please try again later!
Error details:
The page is temporarily unavailable
body { font-family: Tahoma, Verdana, Arial, sans-serif; }
The page you are looking for is temporarily unavailable.
Please try again later.
———————————
Firefox 4b9/Grafx bot 0.1.32
Win 7 x32
Intel 965GM v8.15.10.1930
Xallow
January 17, 2011 at 8:39 pm
There was a server outage this weekend. It’s back up now; sorry for the inconvenience.
jagriffin
January 18, 2011 at 11:10 am
I encountered an error when sending result.
We’re sorry, there was a problem while sending your test results to Mozilla. Please try again later!
Error details:
The page is temporarily unavailable
body { font-family: Tahoma, Verdana, Arial, sans-serif; }
The page you are looking for is temporarily unavailable.
Please try again later.
Alice0775
January 17, 2011 at 9:07 pm
[...] read on FF4 – behind the hood stuff: Graphics, UIfeatures, FF4 vs IE9 – [...]
FF4 RC is here…. « DEMONstrate
March 8, 2011 at 1:15 am
I’m having a problem with Grafx Bot crashing XP. I’m using the latest Firefox, video drivers and DirectX. I’m running the tests in a new profile. I have been able to get partial test results before the machine reboots: http://pastebin.com/pig0BxfZ
The tests continue on past oes-vertex-array-object, crashing somewhere around drawElements – texImage2D. Its hard to tell exactly what test its crashing on because there are several errors past oes-vertex-array-object that scroll by quickly before rebooting.
XP SP3
Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0
DirectX 9.0c (4.09.0000.0904)
Display Vendor: NVIDIA (0x10DE)
Display Adapter: NVIDIA GeForce 6600 GT
Display Chipset: 0×0140
Display RAM: 256 MB
Display Drivers: nv4_disp
Driver Version: 6.14.12.7533, 5-20-2011
Display Settings: 1920 x 1200 x 32
WebGL Renderer: Google Inc. — ANGLE — OpenGL ES 2.0 (ANGLE 0.0.0.611)
GPU Accelerated Windows: 1/1 Direct3D 9
michael
July 8, 2011 at 7:13 pm
Does this crash also occur when using https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/sdk/tests/webgl-conformance-tests.html? If so, could you please file a bug for this at https://bugzilla.mozilla.org?
jagriffin
July 8, 2011 at 9:50 pm
I ran it on a Windows XP desktop with Firefox 5, no problem.
Running it on a laptop running Ubunto 10.10 and Nightly and the “Send” button has no effect.
B.J. Herbison
July 31, 2011 at 3:14 pm
Grafx bot problems:
1. Cannot Send report at end of run. And I’ve got 17 unknowns on a standard fresh Dell build.
2. A major feature missing is some sort of ruler/grid guide for the failed test pictures where text/graphics are moved a pixel or two. It is nearly impossible for users to see if it really failed.
For reference, I’m running 8.0 though
So I sorta don’t expect anyone to fix this 
Mike Huf
August 2, 2011 at 5:36 am
I’d like to help but Grafx Bot is not currently working with the 8.0a1 (2011-08-10) 64 Bit Nightly on Windows 7 that I use. Any plans for adding that?
Martin Forisch
August 10, 2011 at 9:16 am
Currently there aren’t any plans to update GrafxBot for Firefox 8 on any platform, but things may change in the future.
jagriffin
August 10, 2011 at 10:15 am
Then it probably shouldn’t be advertised when starting Nightly: http://www.mozilla.org/projects/firefox/prerelease.html
And addons.mozilla.org says “Doesn’t work with Firefox 3.8″ when trying to install it with a Nightly 8.x…
Arthur
August 20, 2011 at 2:34 am
I agree, I’ll try to have it taken out.
jagriffin
August 20, 2011 at 7:37 pm
@jagriffin, I have a new laptop w/ Linux (Ubuntu) and NVIDIA GeForce GT. At one time I was able to see the sprites in the ‘No Comply’ demo (the dudes fighting) but only in the nightly. The stable was missing those. Now in stable FF 6 and Nightly 9 I can’t see it in either. I would like to run this test suite to maybe help FF add support back again if it was lost but Grafx Bot says it doesn’t work in either FF. Is there still a mechanism for helping test?
Marc Harter (@wavded)
August 21, 2011 at 6:15 pm
GrafxBot has been discontinued as of Firefox 6, but please file a bug about the missing sprites. If you need pointers on how to file one, let me know.
jagriffin
August 21, 2011 at 7:56 pm
Hi. Just some thoughts, apologies if this is not the correct place for bug reporting / feature requests for GrafxBot.
1. It runs the tests fine on Aurora
2. But it seem the submit option is broken.
I came here and see you say ( dated Aug 21 ) that it is discontinued, however, there are recent releases dated October.
So, if it is truely deprecated, it might be nice to have that visible to users so they’re not running the tests needlessly, possibly on the page chrome://grafxbot/content/start-testing.html in the “start testing” button, otherwise its likely to be glossed over.
It may also be nice to have more explicit details on how to deal with user feedback on GrafxBot, lest you keep having your feedback via this blog post, or via negative reviews on AMO.
Hope this helps! =)
– Kent
Kent Fredric
December 25, 2011 at 11:31 am