Tell HN: Chromium nightly (linux) appears to have stable support for Flash
It must've been added within the last couple days.
2 comments
If that's true, then it's a first. Firefox still doesn't have stable support for Flash on Linux. (I kid. A little. But not really.)
Firefox _never_ crashes for me because of Flash since I started always using nspluginwrapper. All that happens at most is the Flash plugin process dies (npviewer.bin). I can also just killall npviewer.bin anytime I want to killall Flash processes. I'm telling everyone!
My sleep timer (for long running Flash streams)
My sleep timer (for long running Flash streams)
# wait 1 hour kill flash turn off LCD
sleep 3600; killall npviewer.bin; xset dpms force standbyActually, it's not really Firefox that has problems. It's mostly just that random crap stops working with Flash. Sound, in particular, just stops working after a day or two.
I actually had a lot more problems with the nspluginwrapper and 32-bit Flash in a 64 bit Firefox (black box after one or two uses of Flash) than I do with the 64-bit Flash build.
It's, admittedly, gotten a lot better over the years, and the 64-bit troubles really only lasted for about 1.5 years (between the time when I moved to 64 bit OS and Adobe released a mostly working 64 bit Flash build; I used a 32 bit Firefox for most of that time). But, it's still pretty common for Flash to cause issues. Going to full screen mode would instantly kill Firefox until just a few weeks ago...and even now, there's no real point to going full screen since it'll be choppy and sluggish, anyway. (And it can't just be the scheduler or the video drivers, since VLC and other media players can do high def full screen without issue.)
I actually had a lot more problems with the nspluginwrapper and 32-bit Flash in a 64 bit Firefox (black box after one or two uses of Flash) than I do with the 64-bit Flash build.
It's, admittedly, gotten a lot better over the years, and the 64-bit troubles really only lasted for about 1.5 years (between the time when I moved to 64 bit OS and Adobe released a mostly working 64 bit Flash build; I used a 32 bit Firefox for most of that time). But, it's still pretty common for Flash to cause issues. Going to full screen mode would instantly kill Firefox until just a few weeks ago...and even now, there's no real point to going full screen since it'll be choppy and sluggish, anyway. (And it can't just be the scheduler or the video drivers, since VLC and other media players can do high def full screen without issue.)
Moreover, when running on a 64-bit OS nspluginwrapper is mandatory, so I have pretty much forgotten how bad Firefox stability used to be.
what are you all talking about? I've been using 64-bit firefox 3.0 (debian's iceweasel) with 64-bit flash (ever since 64-bit flash became available), no nspluginwrapper, and I have no firefox stability troubles at all.
I restart FF every week or so to keep its memory usage down. I typically have 30-50 tabs open at a time. Is it because I use flashblock?
I restart FF every week or so to keep its memory usage down. I typically have 30-50 tabs open at a time. Is it because I use flashblock?
Link: http://build.chromium.org/buildbot/snapshots/
Seems to work on my machine, for the most part.
Seems to work on my machine, for the most part.