Occasional error: Something went wrong with this webpage...

[notestracker]

If your supposition is true, then my (new) occasional lilac-screen errors may be the natural result of the (new) Flash11.03/AB/Win7 error. That makes sense to me. Now, if only that latter error would get resolved by the folks at Adobe, I might be able to get back to the days of having virtually no problems with AB.

I tend to agree that the cause is something wrong with Flash. Even within native Firefox browser, without Avant even being active, Flash crashes from time to time, and there have been releases of Firefox that attempt to solve Flash issues.

When you consider that Avant (in Firefox rendering mode) runs an additional firefox.exe task it's plausible that Flash plug-in interactions between the two could be causing Avant's grey/lilac screen errors at unpredictable times.

[Dreamer]

I tend to agree that the cause is something wrong with Flash. Even within native Firefox browser, without Avant even being active, Flash crashes from time to time, and there have been releases of Firefox that attempt to solve Flash issues.

When you consider that Avant (in Firefox rendering mode) runs an additional firefox.exe task it's plausible that Flash plug-in interactions between the two could be causing Avant's grey/lilac screen errors at unpredictable times.

What do you think about this - 2x flashplayerplugin?

[notestracker]

What do you think about this - 2x flashplayerplugin?

Only two of them that's nothing!

Right at this moment I've got 4 copies of the FlashPlayerPlugin task active (probably 3 in Firefox and 1 in Avant, not completely sure). I wonder what the world record is.

This reminds me of the Monty Python's Flying Circus skit - "Four Yorkshiremen" - Four well-dressed men are sitting together at a vacation resort... http://www.phespirit.info/montypython/f ... iremen.htm

More Monty Python plus many other humor links at my website -- http://notestracker.com/Links/FunnyStuff.htm or http://notestracker.net/Links/FunnyStuff.htm

[Dreamer]

OK, I AM sure the facebook albums are the problem, in the last few weeks, lilac pages appeared while viewing a fb album at least 50 times! I can always reproduce the lilac pages while vieweing a fb album in less than 30 min.. To reproduce, just view any picture from a large fb album, then just click to go to next image.

In build 175 I have about 4-8 crashes every day!! In previous builds it was 1-3 crashes per day.

[Jasmine]

In build 175 I have about 4-8 crashes every day!! In previous builds it was 1-3 crashes per day.

The memory usage before it crashes?
My memory has gone up to more than 800M on facebook while viewing an album, it doesn't crash.

[Dreamer]

Hm.. about 500-900MB. Are you using FF engine?

Don't know, try these steps...

- open 30 tabs
- open 10 more tabs with the FB image
- find the FB album with more than 300 (or more than 500) images
- click the image to go to next image
- repeat 100-200 times

I have the lilac pages with or without FF crash dialog every time I viewing FB albums for 15-30 minutes. Last time few seconds before replying to your post.

[Tinman57]

BTW I think it is worse in this version.

I think you're right about it getting worse in build 175. Not only that, but I'm seeing more crashes in 175 where Avant itself has to be restarted, not just firefox.exe. Stability has definitely decreased with the release of build 175.

Yep, I've had some strange crashes for no apparent reason. Only thing that shows up in Avant and every other app running at the time is a totally greyed out screen. Still have access to the menu-bar and the only way out is to either log off or re-boot. Never had this problem in earlier versions.
I've also hit the lilac pages several time since updating to 175. I had one page that was already loaded and was just fine, switched tabs and did some reading on another page, and when I went back to that first page it was lilac with the "something went wrong" message.

Update: After saving this message I exited the tab and Avant (and everything else) went grey. Then it happened two more times while on this site after closing a tab. This time I was able to get my task manager to show without being greyed out too and force Avant to close. I noticed both times that after the crashed Avant.exe exited, two ybrowsers would open up (without Avant.exe) and would remain there until I forced them to close.
This problem is really getting bad...

Update to the Update: I think a lot of the crashes were coming from my proxy server. A couple of microsoft security updates ago, my proxy started acting strange and eventually wouldn't even work with Avant. I uninstalled that proxy and installed a new one that is much more compatible. I don't get near as many lilac pages now, but I still get the occasional grey screen that pretty much affects all of my windows apps running at the time.
Yesterday I noted that when things went gray, I fired up my task manager and saw that there was one instance of Avant.exe and 3 ybrowsers. I had 5 tabs open at the time. I force killed Avant.exe and the 3 ybrowsers that were showing closed as well. Then 2 more ybrowsers popped up even though Avant had been killed. I had to kill the two ybrowsers as well. My assumption is that while 2 of the last tabs that I opened were still loading when they crashed and took out Avant.exe as well. Why the last two tabs (ybrowsers) didn't show up until after I force killed Avant.exe is anyones guess....
Perhaps this additional info will help the developer figure things out.....

[Dreamer]

OK, this build 175 is really bad, today it crashed 3 times even if I didn't view FB pictures. Last time while writing long post in another forum!

New info - this time the memory usage is quite low, only 200MB, but I had 4x flashplayerplugin running, usually only 2 are running. So it's possible it's flash related.

[Tinman57]

Another update to the update. On the last crash/freeze of Avant a few minutes ago on this forum, every window on every app went solid gray just like Avant. Every time I alt/tab to another open window and click on that window, Avant would pop back to the front window. I would alt/tab back to another app, click it to select that window, and again get taken back to the grayed out Avant. Like before, the only way to get out of all the open gray windows is to force Avant to exit in my task manager....

[Jasmine]

Hm.. about 500-900MB. Are you using FF engine?

Don't know, try these steps...

- open 30 tabs
- open 10 more tabs with the FB image
- find the FB album with more than 300 (or more than 500) images
- click the image to go to next image
- repeat 100-200 times

I have the lilac pages with or without FF crash dialog every time I viewing FB albums for 15-30 minutes. Last time few seconds before replying to your post.

I can't make it crash. Could you disable all extensions and see whether it makes a difference?

[Dreamer]

I can't make it crash. Could you disable all extensions and see whether it makes a difference?

I have tried that already, tested with all extensions disabled, had several crashes and lilac pages - no difference.

[Dreamer]

While trying to update to 176 USB version, Flash Player plugin was not closed properly after closing Avant, so I couldn't update Avant, I had to kill flash player plugin manualy. Perhaps it will help...

[Jasmine]

While trying to update to 176 USB version, Flash Player plugin was not closed properly after closing Avant, so I couldn't update Avant, I had to kill flash player plugin manualy. Perhaps it will help...

Do you mean plugin-container.exe didn't exit after you closed avant browser?

[Dreamer]

No I mean "FlashPlayerPlugin_11_3_300_265.exe" file.

[Jasmine]

Then what conclusion did you get? During flash player installation, Avant Browser can't be upgraded? How did you upgrade avant browser during flash player installation? I can't imagine a conflict between them, unless avant browser intends to open pages with flash videos, which could interfere with the upgrade of the installation of flash plugin.

[Dreamer]

No, it was during Avant USB upgrade, that file didn't close correctly only once (AFAIK), perhaps it might be a problem of the lilac pages.

NEW INFO - in 176 the lilac pages and the FF crash are "delayed" - I mean the tabs are not responding, it's not possible to switch tabs, when I switch tab, the content of the old tab is displayed instead. Such a delay was also in the previous builds but it was just few seconds, in 176 this delay is about 30 seconds - 2 minutes. It is not possible to refresh tabs until FF crash/lilac pages, so it's quite annoying.

[mbrazil]

in 176 the lilac pages and the FF crash are "delayed" - I mean the tabs are not responding, it's not possible to switch tabs, when I switch tab, the content of the old tab is displayed instead. Such a delay was also in the previous builds but it was just few seconds, in 176 this delay is about 30 seconds - 2 minutes. It is not possible to refresh tabs until FF crash/lilac pages, so it's quite annoying.

I'm experiencing this too with build 176. I use the installed version of Ultimate, not the USB version, but the same thing happens fairly frequently.

[brawnymike]

It appears that my two main problems (lilac screen, and superfluous about:blank tab w/stalled startup tabs) are resolved, either by this latest build [177] of AB Ult. 2012 or by the just-released update of Flash Player for Firefox (both of which I installed within the last 24 hours). My suspicion is that the Flash Player update resolved the lilac screen problem and the AB update resolved the about:blank tab problem, not that that matters. All I know is I'm happy, happy, happy.

[Jasmine]

NEW INFO - in 176 the lilac pages and the FF crash are "delayed" - I mean the tabs are not responding, it's not possible to switch tabs, when I switch tab, the content of the old tab is displayed instead. Such a delay was also in the previous builds but it was just few seconds, in 176 this delay is about 30 seconds - 2 minutes. It is not possible to refresh tabs until FF crash/lilac pages, so it's quite annoying.

The problem results from firefox engine. It's possible that the firefox engine is about to crash. Avant Browser is composed of main process(avant.exe) and tab process, if the main process gets no response from the tab process(firefox.exe) after 30 seconds, it will end the tab process. Before the tab process ends, you'll feel a delay.

[mbrazil]

The problem results from firefox engine. It's possible that the firefox engine is about to crash. Avant Browser is composed of main process(avant.exe) and tab process, if the main process gets no response from the tab process(firefox.exe) after 30 seconds, it will end the tab process. Before the tab process ends, you'll feel a delay.

That's very good information to have. Thanks Jasmine!