 |
 |
How threaded is Safari?
|
|
|
|
|
Posting Junkie
Join Date: Jun 2003
Location: Dangling something in the water… of the Arabian Sea
Status:
Offline
|
|
I was just wondering... (Sorry if the terminology is wrong. I'm not a programmer.)
I noticed for quite a while now that if I click on a folder in the bookmarks bar in Safari, all animations simply stop. That includes animated .gifs, flash, etc. Kinda annoying actually. This is not an issue with Firefox.
Is this something that could be fixed quickly, or would this take a major overhaul?
I also note that grabbing the scroll bar also stops all animations. This also happens in Firefox.
Why?
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Jul 2002
Status:
Offline
|
|
Safari used to keep animating while you looked at bookmarks or whatever, but they changed. I guess they decided that animation while you're looking at menus was just a pointless waste of CPU.
As for how thread Safari is, in Tiger on multiprocessor machines, image decoding takes place in (a) separate thread(s). I'm not sure of the specifics, but I know the rendering engine itself isn't threaded at all.
|
|
|
| |
|
|
|
|
|
|
|
Posting Junkie
Join Date: Jun 2003
Location: Dangling something in the water… of the Arabian Sea
Status:
Offline
|
|
Originally Posted by Thinine
Safari used to keep animating while you looked at bookmarks or whatever, but they changed. I guess they decided that animation while you're looking at menus was just a pointless waste of CPU.
So they made a conscious decision to get rid of that? Seems odd.
However, the grab-the-scroll-bar-and-animations-stop thing is even more annoying.
|
|
|
| |
|
|
|
|
|
|
|
Dedicated MacNNer
Join Date: Jul 2004
Location: Ontario, Canada
Status:
Offline
|
|
Originally Posted by Eug Wanker
So they made a conscious decision to get rid of that? Seems odd.
It's a performance improvement, I'm sure it was done consciously.
However, the grab-the-scroll-bar-and-animations-stop thing is even more annoying.
Same deal... scrolling would be slower if it had to animate while the user scrolled.
|
|
|
| |
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Aug 2004
Location: FFM
Status:
Offline
|
|
Originally Posted by Eug Wanker
So they made a conscious decision to get rid of that?
I don't think they did. The Cocoa framework was changed in Panther to not fire timers attached to the main run loop during event tracking. Safari just automatically inherited that change. The application developer can make timers fire during event tracking (again), but it requires a change in the program.
|
|
|
| |
|
|
|
|
|
|
|
Posting Junkie
Join Date: Jun 2003
Location: Dangling something in the water… of the Arabian Sea
Status:
Offline
|
|
Originally Posted by TETENAL
I don't think they did. The Cocoa framework was changed in Panther to not fire timers attached to the main run loop during event tracking. Safari just automatically inherited that change. The application developer can make timers fire during event tracking (again), but it requires a change in the program.
Assuming I understand you....
What's the rational? The extra saved CPU cycles? Where else would this be important?
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
Top
