Post #365,531
10/25/12 6:07:31 PM
|
s/MS/Adobe/
Flash being a crashy pile of shit is Adobe's fault.
|
Post #365,533
10/25/12 6:17:20 PM
|
Flash should just DIE.
--
greg@gregfolkert.net
PGP key 1024D/B524687C 2003-08-05
Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C
|
Post #365,534
10/25/12 6:44:50 PM
|
Yup
|
Post #365,564
10/26/12 10:25:01 AM
|
Flash in the browser, sure.
It's a very nice mobile development platform, though.
Regards, -scott Welcome to Rivendell, Mr. Anderson.
|
Post #365,537
10/25/12 7:48:08 PM
|
Them too. Still, it's MS's OS...
|
Post #365,540
10/25/12 9:37:31 PM
|
***COUGH***COUGH***
--
greg@gregfolkert.net
PGP key 1024D/B524687C 2003-08-05
Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C
|
Post #365,542
10/25/12 9:45:06 PM
|
Robitussin may help with that. ;-)
Explain it to me like I'm stupid. Thanks.
|
Post #365,543
10/25/12 9:47:00 PM
|
Got a "Z-Pack" earlier this week.
--
greg@gregfolkert.net
PGP key 1024D/B524687C 2003-08-05
Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C
|
Post #365,545
10/26/12 1:43:50 AM
|
Re: Them too. Still, it's MS's OS...
App crashes are not the problem of the OS vendor.
|
Post #365,551
10/26/12 7:02:07 AM
|
True but...
Yeah, I've got a weak argument, but bear with me.
The error/crash only occurs when Taskbar Shuffle is used with Flash.
It seems to happen with Firefox, Chrome, and IE8 (dunno if TS is always installed nor whether it always involves Flash, but those seem to be the most common intersections).
It seems to me to be an API issue. The API is either written in such a way that it's easy for Flash to stomp on shared memory used by TS, or Adobe is trying to do something it shouldn't.
MS has control over the Win32 API. The OS controls what is legal or not.
Either MS's API needs to be tightened up to prevent Flash apps from stomping on someone else's shared memory, or Adobe needs to be slapped down for doing things outside the standard API.
This problem has been going on for years. Lots of people have this trouble, but the actual solution is very hard to find and not widely known. It shouldn't still be happening.
Adobe is the logical person to fix this, but if the OS and API were better then it wouldn't show up on the user's desktop at all. It would have been caught in the build process AFAICS.
And if MS hadn't broken their taskbar functionality over the years, then TS wouldn't be needed...
FWIW.
Cheers,
Scott.
|
Post #365,552
10/26/12 7:24:08 AM
|
Re: True but...
The OS is probably doing the right thing here, but the apps in question aren't dealing with their situation gracefully (and OMG my IE10 textbox has got autocorrect >high fives MS<), instead crashing.
|
Post #365,554
10/26/12 8:31:06 AM
|
Snark
High five, MS has caught up to FirFox from (at least) five years ago! WOOOO!
--
Drew
|