page speed crashes with some 64-bit windows7 installs

[GoogleCodeExporter]

What steps will reproduce the problem?  If possible, include the full Url
of any web page you see a problem on.
1. visit -any- url (except about:blank)
2. open firebug
3. select the Page Speed tab
4. click Analyze Performance

What is the expected output? What do you see instead?
It immediately crashes Firefox

What version of Firefox are you using?  From the 'Help' menu, select 'About
Mozilla Firefox' to get the version.
3.6

What version of Firebug are you using?  From the 'Tools' menu, select 'Add-
ons', and click on 'Extensions'.  Firebug and its version should be listed.
1.5.2

What version of Page Speed are you using?  Follow the procedure to get the
Firebug version, and look for 'Page Speed' in the list of extensions.
1.6

What operating system are you using?
Windows 7 x64

Please provide any additional information below.
The only 'url' that doesn't crash Firefox after hitting the "Analyze
Performance" button is about:blank

Original issue reported on code.google.com by valentij...@gmail.com on 8 Mar 2010 at 2:35

[GoogleCodeExporter]

Update:
Running Firefox as Administrator solves the issue.

Note:
After having ran Pagespeed 1.6 in Administrator mode I tried running
it again in normal mode. 
Result:
Now firefox just hangs and becomes completely irresponsive at the "running 
minify
javascript" step

Original comment by valentij...@gmail.com on 12 Mar 2010 at 11:58

[GoogleCodeExporter]

what cpu?

Original comment by rab...@google.com on 21 Apr 2010 at 4:21

[GoogleCodeExporter]

-- what cpu?
Intel Core 2 Quad Q9300 @ 2.50GHz

Original comment by valentij...@gmail.com on 21 Apr 2010 at 8:19

[GoogleCodeExporter]

Can you try version 1.8 available as a beta download?

Original comment by rab...@google.com on 18 May 2010 at 5:45

[GoogleCodeExporter]

Issue 219 has been merged into this issue.

Original comment by bmcqu...@google.com on 25 May 2010 at 8:43

[GoogleCodeExporter]

Issue 259 has been merged into this issue.

Original comment by bmcqu...@google.com on 25 May 2010 at 8:45

[GoogleCodeExporter]

I've tested this on one 64bit win7 box and had no issues, but clearly there are 
some 
issues for some users. We'll test on more win7 boxes to see if we can 
reproduce. 

Original comment by bmcqu...@google.com on 26 May 2010 at 12:42

• Changed title: compatibility issues with 64-bit windows7

[GoogleCodeExporter]

I wonder if it is a combination of using a 64 bit processor running 32 bit 
version of
windows 7.  My computer is an Intel i7-860, but I run the 32bit version of 
windows 7.

Original comment by presiden...@gmail.com on 26 May 2010 at 2:03

[GoogleCodeExporter]

I haven't used Pagespeed in a while, but just noticed the issue has been 
resolved on
my machine. 

I'm currently using:
Firefox 3.6.3
Firebug 1.5.4
Pagespeed 1.7.1

I've also tried the 1.8.2 beta as you requested: works fine too,.. no problems 
at all.

I'm not sure what has changed, but everything works again, so thanks for your 
support!

Summary of system specs and version info:
O.S: Windows 7 x64
CPU: Intel Core 2 Quad Q9300 @ 2.50GHz (64bit)
Problem occured while using: 
- Firefox 3.6
- Firebug 1.5.2
- Pagespeed 1.6
Problem was resolved while using the latest versions:
- Firefox 3.6.3
- Firebug 1.5.4
- Pagespeed 1.7.1 or 1.8.2 beta

Original comment by valentij...@gmail.com on 26 May 2010 at 2:13

[GoogleCodeExporter]

Interesting. I wonder if the root cause was the same as this issue: 
http://code.google.com/p/page-speed/issues/detail?id=258

We fixed this issue in the 1.7.1 release. Would you mind temporarily installing 
1.7.0 
and testing, to see if 1.7.0 crashes for you? If the issue is present in 1.7.0 
but not 
in 1.7.1 or later then it should be due to issue 258.

https://dl-ssl.google.com/page-speed/1.7.0.0/page-speed.xpi

Original comment by bmcqu...@google.com on 26 May 2010 at 2:26

[GoogleCodeExporter]

Still crashing.

Firebug 1.5.4
Page speed 1.7.1
have Google toolbar for Firefox 7.1.20100408wb1
Firefox 3.6.3

Windows 7 Professional
32 bit operating system
Intel i7-860 (64bit processor)
Dell Optiplex 980 (new computer)
4 GB memory

I uninstalled pagespeed and firebug and reinstalled the above versions.  Still
crashes on any web page when analyze is clicked.

bmcqu...@google.com, want to remote desktop and see it first hand?

Scott

Original comment by presiden...@gmail.com on 26 May 2010 at 2:55

[GoogleCodeExporter]

Just tried uninstalling Pagespeed 1.7.1 and installing 1.8.2, still crashes.

Scott

Original comment by presiden...@gmail.com on 26 May 2010 at 2:59

[GoogleCodeExporter]

B.H.

Firefox 3.6 is known to have problems on 64bit windows7 systems (AFAIK, no 
matter if
firebug/pagespeed etc is installed). The lastest updates of FF 3.6. seem to be 
more
stable. At least, on my computer (with win7 64 bit) i have the lastest FF 3.6,
firebug and pagespeed  and have no issues.

Original comment by mkaganer on 27 May 2010 at 11:34

[GoogleCodeExporter]

If you're experiencing crashes and you've upgraded to the most recent 
Firefox/Firebug/Page Speed, can you list the other Firefox add-ons you have 
installed? 
Perhaps we have a compatibility issue that only manifests itself on 64bit Win7.

Original comment by bmcqu...@google.com on 27 May 2010 at 2:02

[GoogleCodeExporter]

Firefox 3.6.3
Add-on's:
Firebug 1.5.4
Google Toolbar for firefox 7.1.20100408Wb1
Page Speed 1.8.2

Plug-in's:
Adobe Acrobat 9.3.2.163
Google Update 1.2.183.23
Itunes application detector 1.0.1.1
Mozilla default plug-in 1.0.0.15
QuickTime 7.6.6.0
Shockwave Flash 10.0.45.2
Silverlight 3.0.50106.0

Scott

Original comment by presiden...@gmail.com on 27 May 2010 at 2:18

[GoogleCodeExporter]

copying from bug 259 so we don't lose track:

2.5 year old HP laptop
Intel Core2 TZ200
4gb memory

Windows 7 64bit

Firefox 3.6.3
Firebug 1.5.4
Page Speed 1.8.3

Addons:
Ablock Plus 1.2
FiddlerHook 2.2.8.2
FireShot 0.80
Html Validator 0.8.6.1
Java Console 6.0.17
Viewstate Size 1.0.1
Web Developer 1.1.8

Original comment by bmcqu...@google.com on 4 Jun 2010 at 1:32

• Changed title: page speed crashes with some 64-bit windows7 installs

[GoogleCodeExporter]

Would just like to add a vote and confirm I am experiencing exactly the same 
issue - 

Win7 64bit, 
Firefox 3.6.8,
Firebug 1.5.4,
Pagespeed 1.8.3

Addons: various, but i have systematically disabled them all trying to get this 
to work until only firebug and pagespeed were there and it still crashed. 

(Listed those reenabled anyway, just FYI)
All-in-One Sidebar 0.7.11
ColorZilla 2.0.2
FireQuery 0.7
IE Tab Plus 1.92.20100607
Java Console 6.0.20
Pixel Perfect 1.5.6
Web Developer 1.1.8
YSlow 2.0.7

Running as an Administrator makes no difference whatsoever.
Neither do the various Compatibility mode emulations(Tried XP sp3,vista,vista 
sp2) 

It also will usually(but not always) work the very first time FireFox is 
started after a reboot, but after that first run, it crashes consistently and 
without fail (please excuse the tautology). 

If memory dumps or any other information I can provide will help, I will gladly 
supply them, I remember using Pagespeed back in the day on my desktop running 
vista 32 and it was awesome. I would love to see how the integrated closure 
compiler works(that wasn't implemented when last i tried pagespeed).

If you think it would be helpful, I could try installing progressively older 
versions of Pagespeed until i find one that works, but its a PITA and I don't 
fancy goose-chasing if it won't provide helpful information.

Hardware:
Acer Aspire 8930G Laptop
CPU: Core 2 Duo T6400 @ 2Ghz
Ram: 4GB DDR3
GPU: Nvidia 9600M GT

PS: Is there anyway to disable the closure compilation during the analysis(or 
to be able to select only the analyses we are interested in), as it seems that 
is where it is mostly bombing out - minifying javascript.

Original comment by joebon...@gmail.com on 4 Aug 2010 at 3:51

[GoogleCodeExporter]

Happening to me. 

Win 7 64 bit
ff 3.6.8
ps 1.8
fb 1.5.4

tons of addons

AMD Athlon II X4 630
4 GB
GTS 250

Willing to provide more 411 if it helps.

Original comment by uncoolce...@gmail.com on 31 Aug 2010 at 11:51

[GoogleCodeExporter]

We have a prerelease version of Page Speed 1.9 for testing. Can you try it on 
Win7 and see if the crash issue is still present?

https://dl-ssl.google.com/page-speed/1.9.0.0/page-speed.xpi

Original comment by bmcqu...@google.com on 17 Sep 2010 at 7:35

[GoogleCodeExporter]

Still no dice - see attached screencast:

http://www.screencast.com/users/joebone/folders/Jing/media/ba2d51dd-8a02-4efe-89
42-fb0ababa66e0

Original comment by joebon...@gmail.com on 19 Sep 2010 at 12:07

Attachments:

• Pagespeed_1.9_firefox_crash.swf

[GoogleCodeExporter]

Thanks for the video. Given that it posted a crash report, would you be willing 
to post the contents of your Firefox about:crashes here? That might help me 
find the crash report which should let me reconstruct the stack trace to 
identify the offending code.

Original comment by bmcqu...@google.com on 19 Sep 2010 at 1:07

[GoogleCodeExporter]

Still using 1.8 and 3.6.8 but not crashing any more. Interesting.

Original comment by uncoolce...@gmail.com on 19 Sep 2010 at 4:30

[GoogleCodeExporter]

Glad to hear it is no longer crashing. Did anything change? e.g. did you 
install/uninstall any add-ons between now and then?

if anyone else experiences this crash, can you please send me the relevant info 
from about:crashes so i can debug the crash dump. if i can get some sample 
crash dumps, we should be able to get this fixed.

Original comment by bmcqu...@google.com on 20 Sep 2010 at 2:40

[GoogleCodeExporter]

I was able to find some example crashes in the crash database. We will begin 
debugging those.

Original comment by bmcqu...@google.com on 20 Sep 2010 at 2:41

[GoogleCodeExporter]

I have 35 active addons, so I'm sure a few received updates in the two-plus 
weeks between crashes and my new happy place. I'm happy to provide any info to 
help you troubleshoot, but I fear it'll have to come from logs. My episodic 
memory for minutia like addons is suspect at best ;)

Original comment by uncoolce...@gmail.com on 20 Sep 2010 at 3:00

[GoogleCodeExporter]

np - you mean the actual links?

these were the two from the video I believe, although I have since updated to 
3.6.10 - will force a crash and post that too in a sec. Access violations seem 
to be the name of the game..

http://crash-stats.mozilla.com/report/index/bp-73a31144-1521-4823-998c-95fc22100
919
http://crash-stats.mozilla.com/report/index/bp-e0ff999e-058f-44a9-8535-09a332100
919

I should probably check my email more often too.

Original comment by joebon...@gmail.com on 21 Sep 2010 at 8:08

[GoogleCodeExporter]

Crash report for 3.6.10: 
http://crash-stats.mozilla.com/report/index/bp-c7393505-9ade-49d5-8626-265f12100
921

Original comment by joebon...@gmail.com on 21 Sep 2010 at 8:10

[GoogleCodeExporter]

Thank you for the links. I just worked with some people at Mozilla to get our 
debug symbols loaded into their crash dump server. Could you trigger a few more 
crashes and share the links? New crashes should have symbols which will help us 
debug. It seems that because these are release builds, the line numbers in the 
stack traces aren't always accurate.

Thanks!

Original comment by bmcqu...@google.com on 21 Sep 2010 at 2:14

• Changed state: Accepted

[GoogleCodeExporter]

BTW here is a decoded stack trace. It points to a call to nsIURL::GetSpec() but 
I am suspicious that it's the actual crash point. Still, it's somewhere inside 
SerializeToFile. Perhaps it's just a file access issue...

Original comment by bmcqu...@google.com on 21 Sep 2010 at 2:17

[GoogleCodeExporter]

0044d6c8 03e25009 pagespeed!`anonymous 
namespace'::PluginSerializer::SerializeToFile(class 
std::basic_string<char,std::char_traits<char>,std::allocator<char> > * 
content_url = 0x00004269, class 
std::basic_string<char,std::char_traits<char>,std::allocator<char> > * 
mime_type = 0x03f9097c, class 
std::basic_string<char,std::char_traits<char>,std::allocator<char> > * body = 
0x00000008)+0x74 
[c:\src\psff19\src\pagespeed_firefox\cpp\pagespeed\pagespeed_rules.cc @ 122]
0044d8b4 03e4c42e 
pagespeed!pagespeed::formatters::JsonFormatter::NewChild(class 
pagespeed::FormatterParameters * params = <Memory access error>)+0x8a9 
[c:\src\psff19\src\third_party\libpagespeed\src\pagespeed\formatters\json_format
ter.cc @ 238]
0044d8c4 03e441c1 pagespeed!pagespeed::Formatter::AddChild(class 
pagespeed::FormatterParameters * params = <Memory access error>)+0x2e 
[c:\src\psff19\src\third_party\libpagespeed\src\pagespeed\core\formatter.cc @ 
171]
0044db1c 03e4db2f pagespeed!pagespeed::rules::MinifyRule::FormatResults(class 
std::vector<pagespeed::Result const *,std::allocator<pagespeed::Result const *> 
> * results = <Memory access error>, class pagespeed::Formatter * formatter = 
<Memory access error>)+0x4d1 
[c:\src\psff19\src\third_party\libpagespeed\src\pagespeed\rules\minify_rule.cc 
@ 149]
0044dbe0 03e4e2dc pagespeed!pagespeed::`anonymous 
namespace'::FormatRuleResults(class std::vector<pagespeed::Result const 
*,std::allocator<pagespeed::Result const *> > * rule_results = 0x00000000, 
class pagespeed::InputInformation * input_info = 0x0404dde8, class 
pagespeed::Rule * rule = 0x0000001d, class pagespeed::RuleFormatter * formatter 
= 0x0000001d)+0x12f 
[c:\src\psff19\src\third_party\libpagespeed\src\pagespeed\core\engine.cc @ 67]
0044dd64 03e4e40b pagespeed!pagespeed::Engine::FormatResults(class 
pagespeed::Results * results = 0x00000000, class pagespeed::RuleFormatter * 
formatter = 0x0404dde8)+0x21c 
[c:\src\psff19\src\third_party\libpagespeed\src\pagespeed\core\engine.cc @ 167]
0044de8c 03e09864 pagespeed!pagespeed::Engine::ComputeAndFormatResults(class 
pagespeed::PagespeedInput * input = <Memory access error>, class 
pagespeed::RuleFormatter * formatter = <Memory access error>)+0xcb 
[c:\src\psff19\src\third_party\libpagespeed\src\pagespeed\core\engine.cc @ 179]
0044e10c 0fbf2e98 
pagespeed!pagespeed::PageSpeedRules::ComputeAndFormatResults(char * data = 
<Memory access error>, class nsIArray * input_streams = <Memory access error>, 
char * root_url = <Memory access error>, class nsIDOMDocument * root_document = 
<Memory access error>, short filter_choice = <Memory access error>, class 
nsILocalFile * output_dir = <Memory access error>, char ** _retval = <Memory 
access error>)+0x254 
[c:\src\psff19\src\pagespeed_firefox\cpp\pagespeed\pagespeed_rules.cc @ 224]
0044e150 0fa8f6bd xul!NS_InvokeByIndex_P(class nsISupports * that = 0x04047c68, 
unsigned int methodIndex = 3, unsigned int paramCount = 7, struct nsXPTCVariant 
* params = 0x0044e200)+0x27 
[e:\builds\moz2_slave\win32_build\build\xpcom\reflect\xptcall\src\md\win32\xptci
nvoke.cpp @ 103]
0044e3e8 0fa8c4e3 xul!XPCWrappedNative::CallMethod(class XPCCallContext * ccx = 
0x0044e418, XPCWrappedNative::CallMode mode = CALL_METHOD (0))+0x4fd 
[e:\builds\moz2_slave\win32_build\build\js\src\xpconnect\src\xpcwrappednative.cp
p @ 2722]
0044e4b4 711d86fd xul!XPC_WN_CallMethod(struct JSContext * cx = <Memory access 
error>, struct JSObject * obj = <Memory access error>, unsigned int argc = 
<Memory access error>, int * argv = <Memory access error>, int * vp = <Memory 
access error>)+0x173 
[e:\builds\moz2_slave\win32_build\build\js\src\xpconnect\src\xpcwrappednativejso
ps.cpp @ 1740]
0044e568 711dd3fb js3250!js_Invoke(struct JSContext * cx = 0x05f97000, unsigned 
int argc = 6, int * vp = 0x0b9bc244, unsigned int flags = 2)+0x42d 
[e:\builds\moz2_slave\win32_build\build\js\src\jsinterp.cpp @ 1360]
0044e7b4 711d8556 js3250!js_Interpret(struct JSContext * cx = 
0x05f97000)+0x298b [e:\builds\moz2_slave\win32_build\build\js\src\jsops.cpp @ 
2241]
0044e858 711c9753 js3250!js_Invoke(struct JSContext * cx = 0x05f97000, unsigned 
int argc = 1, int * vp = 0x0b9bc064, unsigned int flags = 0)+0x286 
[e:\builds\moz2_slave\win32_build\build\js\src\jsinterp.cpp @ 1368]
0044e8ac 711dbbaa js3250!js_fun_apply(struct JSContext * cx = 0x05f97000, 
unsigned int argc = 1, int * vp = 0x0b9bc02c)+0x293 
[e:\builds\moz2_slave\win32_build\build\js\src\jsfun.cpp @ 2047]
0044eadc 711d8556 js3250!js_Interpret(struct JSContext * cx = 
0x05f97000)+0x113a [e:\builds\moz2_slave\win32_build\build\js\src\jsops.cpp @ 
2208]
0044eb80 0fa8b674 js3250!js_Invoke(struct JSContext * cx = 0x05f97000, unsigned 
int argc = 1, int * vp = 0x0b9bc020, unsigned int flags = 0)+0x286 
[e:\builds\moz2_slave\win32_build\build\js\src\jsinterp.cpp @ 1368]
0044edb8 0fa7c488 xul!nsXPCWrappedJSClass::CallMethod(class nsXPCWrappedJS * 
wrapper = 0x07308a00, unsigned short methodIndex = 3, struct 
XPTMethodDescriptor * info = 0x02e6f4e0, struct nsXPTCMiniVariant * 
nativeParams = 0x0044edf4)+0x854 
[e:\builds\moz2_slave\win32_build\build\js\src\xpconnect\src\xpcwrappedjsclass.c
pp @ 1697]
0044edd0 0fbf30e0 xul!nsXPCWrappedJS::CallMethod(unsigned short methodIndex = 
0x1130, struct XPTMethodDescriptor * info = 0x00000003, struct 
nsXPTCMiniVariant * params = 0x0044eeac)+0x38 
[e:\builds\moz2_slave\win32_build\build\js\src\xpconnect\src\xpcwrappedjs.cpp @ 
571]
0044ee84 0fbf3147 xul!PrepareAndDispatch(class nsXPTCStubBase * self = 
0x08321130, unsigned int methodIndex = 3, unsigned int * args = 0x0044eeac, 
unsigned int * stackBytesToPop = 0x0044ee9c)+0xe7 
[e:\builds\moz2_slave\win32_build\build\xpcom\reflect\xptcall\src\md\win32\xptcs
tubs.cpp @ 114]

Original comment by bmcqu...@google.com on 21 Sep 2010 at 2:21

[GoogleCodeExporter]

This looks a bit like a crash we'd experienced when attempting to write to 
files using file descriptors on Windows. I'm going to put together a change and 
create a custom build for you to test, to see if it resolves the issue.

Original comment by bmcqu...@google.com on 21 Sep 2010 at 2:59

[GoogleCodeExporter]

This looks a bit like a crash we'd experienced when attempting to write to 
files using file descriptors on Windows. I'm going to put together a change and 
create a custom build for you to test, to see if it resolves the issue.

Original comment by bmcqu...@google.com on 21 Sep 2010 at 2:59

[GoogleCodeExporter]

I've attached a custom build that might fix the crash issue. Can someone 
experiencing the crashes install this XPI (it only works in Windows) and let me 
know if it fixes the crash?

Original comment by bmcqu...@google.com on 21 Sep 2010 at 3:48

Attachments:

• page-speed.xpi

[GoogleCodeExporter]

To install, you may need to download the file to your local disk then open the 
saved file in Firefox (File->Open File...).

Original comment by bmcqu...@google.com on 21 Sep 2010 at 3:51

[GoogleCodeExporter]

As a workaround: I had to set the path for "Save Optimized Files To: 
C:/Users/..../AppData/Local/Temp"
and then deleted all files from this temp folder. After this the crash was 
resolved. So the issue is with writing files. 

Also the problem occurs for several sites, so is not a site specific issue. 
Hope this helps.

Original comment by kundan...@gmail.com on 24 Sep 2010 at 6:53

[GoogleCodeExporter]

Well i tried the 1.9pre+svn above, still no joy. i thought it may have been a 
file access issue earlier(when creating the compressed JS files with closure 
perhaps?) which is why i was running in administrator mode, but didn't seem to 
make a blind bit of difference.

anyhoo - latest report:
http://crash-stats.mozilla.com/report/index/610c8e49-b3ad-4bc8-a33f-f55a22100926

Original comment by joebon...@gmail.com on 26 Sep 2010 at 3:22

[GoogleCodeExporter]

Original comment by mdste...@google.com on 28 Sep 2010 at 2:48

• Added labels: Component-Lib, OpSys-Windows

[GoogleCodeExporter]

small update - i reverted to the stable firebug build(1.5.4), ran page speed on 
their page - http://getfirebug.com/ and VOILA! it worked without crashing! So i 
got all excited but then came and ran it on  THIS page 
(http://code.google.com/p/page-speed/issues/detail?id=252&sort=priority&colspec=
ID%20Type%20Status%20Priority%20Component%20Milestone%20Owner%20Summary%20Stars#
makechanges) and it died the same old horrible repeatable death.

So there is definitely certain content that it just does not like.

Original comment by joebon...@gmail.com on 28 Sep 2010 at 8:58

[GoogleCodeExporter]

Issue 345 has been merged into this issue.

Original comment by bmcqu...@google.com on 29 Sep 2010 at 8:37

[GoogleCodeExporter]

joeboneuk, I tried THIS page. It has no problem for me. We will keep looking 
for what is the bug. 

Original comment by ls...@google.com on 29 Sep 2010 at 8:44

[GoogleCodeExporter]

Sure :) I am sure it has no problem for most people hehe otherwise it wouldnt 
have been released. I would love to know what it is in my particular setup that 
is causing it though. Running the latest firebug 1.7X.0a2 alpha doesn't crash 
on the firebug page, but it gets 0/100 with 
"Defer Javascript"
"100% of the JavaScript loaded by this page had not been invoked by the time 
the onload handler completed."
2 other rules are run:
"Remove unused CSS" and "Use efficient CSS selectors" throw this error:
Sorry, there was an error while running this rule. Please file a bug with these 
details: TypeError: context is undefined (chrome://firebug/content/lib.js:3096)

running this page still crashes:
http://crash-stats.mozilla.com/report/index/d6c3120f-c514-4d25-988e-f275c2100929

Original comment by joebon...@gmail.com on 29 Sep 2010 at 9:48

[GoogleCodeExporter]

Original comment by bmcqu...@google.com on 30 Sep 2010 at 4:30

• Added labels: Component-Firefox, Milestone-1.9, Priority-High
• Removed labels: Component-Lib, Priority-Medium

[GoogleCodeExporter]

We just pushed version 1.9.1 which should fix this issue. Can you please give 
it a try and let us know?

https://dl-ssl.google.com/page-speed/1.9.1.0/page-speed.xpi

Original comment by bmcqu...@google.com on 6 Oct 2010 at 12:54

[GoogleCodeExporter]

FYI  While 1.9 re-broke it for me, 1.9.1 works again. Thanks.

Original comment by uncoolce...@gmail.com on 6 Oct 2010 at 3:10

[GoogleCodeExporter]

Woot, well done guys, can confirm this has fixed the crash issues for me - have 
noticed a slight inconsistency - firefox 3.6.10 gives this page 83/100, whereas 
4 beta 6 gets 87/100, but thats another issue, and the crash bug is fixed for 
me :) 
Nice one!

Original comment by joebon...@gmail.com on 6 Oct 2010 at 8:11

[GoogleCodeExporter]

Thanks for the confirmation.

Original comment by ls...@google.com on 6 Oct 2010 at 1:18

• Changed state: Fixed

[GoogleCodeExporter]

Fixed for me also.  Tried all intermediate versions previously announced, none 
worked until now!  Thanks! (Windows 7, 64 bit machine, 32 bit OS)

Original comment by presiden...@gmail.com on 6 Oct 2010 at 1:28