Octane 2 benchmark crashes Firefox 36 Win64.

[streetwolf]

Have a look at this bug report I opened regarding the crash... 1096312 – Crash in Octane 2.0 benchmark demo. As I indicated it 'might' be AG related.

If you can install the latest version, link is in my last comment, and see what happens when you run Octane 2. It's possible the 'bad' patch made it to the regular Nightly branch, possibly win32 and win64. I haven't tried these.

 

[Boo Berry]

Odd, I just tried this with the latest Nightly 64-bit build and it doesn't crash for me (e10s enabled, no extensions, Adguard with filter lists in sig enabled). Which filter lists are you using? I'd try disabling all filters, then retry the test. If it crashes/works start enabling filters one-by-one. If all else fails, add this rule to your user filter to whitelist the site;

@@||octane-benchmark.googlecode.com$document

P.S. I've noticed the assistant doesn't show up on that site. Also, by default shouldn't these benchmark sites be whitelisted to avoid possible issues when benching? What do you think, avatar?

 

[streetwolf]

Hey Boo.

First off the Nightly build you used might not have the patch that I think is causing the problem. You should try the latest one here that has the patch... Index of /pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-win64-pgo

I added the filter and Octane works, for now. If you read the Mozilla bug report I opened I did a clean boot of my system with only MS stuff running and I still crashed. That's what leads me to think that AG is leaving something around that causes the crashes. I've gotten Octane to work at times without your filter, but only for a short time. Invariably the crashes came back. I wouldn't be surprised at all, even with your filter, that I will crash again.

Just had a thought. Maybe something in Firefox is retained that causes crashes when none should happen. Stored links, cookies, whatever. A clean profile never had the crashes.

 

[streetwolf]

Adding the filter seems to have solved my crashes. But the question still begs, why did the Mozilla patch cause the crashes in the first place?

 

[Boo Berry]

Nightly is crashing for me on Octane 2.0 regardless if Adguard is enabled or not.

---------- Post added at 06:39 PM ---------- Previous post was at 06:29 PM ----------

I'm going to try a new Nightly profile and try to narrow this down to either a Nightly bug or an incompatibility with Adguard. Nonetheless, I feel the exception rule I posted which fixed it for you should probably be pushed to the filters. Thoughts, avatar?

---------- Post added at 06:50 PM ---------- Previous post was at 06:39 PM ----------

Okay, yes, I can confirm that somehow Adguard is causing Octane 2.0 to crash today's Nightly. I ran Adguard in debug mode and looked for anything interesting but alas there was no errors or anything. Still, the exception rule I posted does seem to indeed work around this issue.

 

[avatar]

Does it crash even if the site is whitelisted in AG?

 

[Boo Berry]

Does it crash even if the site is whitelisted in AG?

Nope.

 

[streetwolf]

Avatar... if you read the Mozilla bug report I opened in my first post above, you will see how strange this crash was for me.

 

[avatar]

I think that we should just whitelist the benchmark.

AG injects it's own JS and CSS which could mess with benchmark code.

That's what leads me to think that AG is leaving something around that causes the crashes.

Something could be left in browser cache.

 

[streetwolf]

For the last two days I've been getting this warning message in my Event Log:

A TDI filter (\Driver\adgnetworktdi) was detected. This filter has not been certified by Microsoft and may cause system instability

I think the problem started when I was trying to narrow down why Octane 2 was crashing. When I did a clean boot of Windows I temporary disabled adgnetworktdi in order to rule out AG as the problem. How can I fix things so I don't get this message?

 

[avatar]

For the last two days I've been getting this warning message in my Event Log:

A TDI filter (\Driver\adgnetworktdi) was detected. This filter has not been certified by Microsoft and may cause system instability

I think the problem started when I was trying to narrow down why Octane 2 was crashing. When I did a clean boot of Windows I temporary disabled adgnetworktdi in order to rule out AG as the problem. How can I fix things so I don't get this message?

You can switch to WPF driver.

Anyway the message is nothing serious.

 

[streetwolf]

I see that my WPF option is unchecked. Guess I did this during my testing. Thanks for pointing me in the right direction.

 

[streetwolf]

t looks like 1095973 – crash @ PurgeProtoChain fixed the problem. Don't need to whitelist the Octane site anymore. This patch is in the latest Nightly.

 

[Boo Berry]

Ah, excellent!

But since it's a benchmark, it probably should be whitelisted anyways.