[Macola]

I recently downloaded 0.8 final (I was previously using 0.8b) and noticed a lot of disk activity every time I launched Camino. I ran top and the process responsible appears to be update_prebinding, which runs for almost a minute after launching Camino. Has anyone else noticed this?

[wataru]

That's not specific to Camino. update_prebinding will automatically run any time you launch an app that isn't prebound. update_prebinding attempts to prebind it; if successful, it won't happen again (until you update the app).

What exactly being "bound" means, I have no idea. But it has to do with the speed with which apps can be launched. The "Optimization" step when installing .pkg's is where the OS updates the prebinding on what you just installed; one of the reasons OS X 10.0 was so slow for many people was that if you didn't install the developer tools your system didn't get prebound and app launching was like molasses.

[Macola]

Originally posted by wataru:
That's not specific to Camino. update_prebinding will automatically run any time you launch an app that isn't prebound.

Right, I realize that. Just curious why it wasn't a problem with the nightlies and happened after I installed the final.

[dole]

# A bug in 10.3's built-in pre-binding script requires Camino to run its own at startup. The first time you run Camino, it may take several minutes to complete depending on the speed of your machine as it works in the background. You will notice a high amount of disk activity while it is pre-binding. The end result will be much improved startup times for every subsequent launch.

I got that from here.

[Macola]

Thanks! I guess I should read the release notes next time

[Krypton]

This has started happening with the latest Firefox builds too... yet about a month ago this didn't happen with 10.3