OSStatus error -108 in QuickTime while trying to record my desktop.

Error -108 stands for "Memory Full"

Screen recording requires creating large buffers of memory. It's probably the cause of the problem.

See also: http://aeroquartet.com/movierepair/quicktime-errors

-- Benoît

I am still fighting with this one, any suggestions?

As previously mentioned, the error message refers to a "ran out of memory" error—specifically, "not enough room in the heap memory." This may indicate you need to manually optimized the drive being use for the RAM cache allocation to remaximize the availability of "contiguous" memory space. (I.e., your drive may be overly fragmented at this time.)

No seriously OSX does not need defragmentation according to Apple. Or?

They also say it dpesn't suffer memory leakage...

I also have 60GB of free space on my OS HD. So could it really be that there is no space?

Its not that there isn't enough memory but that it is not contiuous/optimally located on your drive. Am only passing on what others have reported. Have also read that it can be caused by PRAM maintanence problems or conflicts with third-party apps like Flip4Mac. All I know for sure is that I "optimize" my drives when the readings hit the 33%-37% range for my internal and external non-RAID drives and have not received any such messages.

you write 'PRAM maintenance problems', you mean a pram zap might do it?

At least one individual claimed it fixed his problem. Top solution was manually optimizing drives to maximize contiguous blocks of space. This solution most often referenced by iMovie users who were unable to "finalize" exports but also mentioned in reference to QT conversions unable to "finalize" files and screen captures to a lesser degree. (I use SnapzPro X and ScreenFlow for screen chaptures and have not seen this problem.)

What do you suggest one uses to optimize?

TechTool seemed to be recommended most often. (I use DiskWarrior to completely rebuild/image directory, graph, optimize, repair, and test non-RAID drives.)

OK just zapped the PRam, no Cigar.

Personally, I did not think it would help. (As previously noted, I tend to agree with those who consider this more of a "contiguous" memory problem.)

see the 10.6.8 was installed freshly about 3 weeks ago. this MM functions as a server doing faxes, answering machine, print server and a few emails a day (iMovie is not even installed neither is Flip4Mac). so it is not like in heavy use. so I fail to see how their can be fragmentation.

Did you "wipe" the drive prior to your install? If not, there is the possibility of carryover fragmentation. I just checked my startup drive and found 709,236 of 1,991,704 items out of optimum order (36%) since my last routine maintainence optimization, drive mechanics test, and general "dusting & cleaning" exercise. Here is the graph:

Of course, I may process an average of 100 GBs to 200 GBs of data during a typical day of copying, converting, and storing video content. (Yesterday was a non-typical day since I had to "panic" backup 597 GBs of DVD images from one RAID drive to another because one array appeared to require reformatting following its latest firmware and dashboard updates. This was in the middle of copying a season of TV shows to my internal drive, converting them for TV use, adding them to my iTunes library, inserting metadata, and proofing the results. In any case, it appears my DroboPro will survive after all since I discovered this morning that the dashboard installer app as released by manufacturer support was probably faulty. (I.e., the embedded PKG file embedded within the installer application was opening Pacifist for installation rather than the Mac OS Installer.app as it should have done. In any case, I extracted the installer package from the app file, corrected the problem, and ran the PKG file manually to save the need of backing up another 7 TBs of data over the next week.)

In any case, to get back to your problem... It may be a good idea to simply see if you can find a program that will graph, disply, or otherwise reveal your current state of fragmentation. If the disk is not fragmented, then you can continue your search for an alternative solution. If it is highly fragmented, then you can try the defragmentation option and see it it works. In either case, it may help others if you post your results here for further review.

Best of luck...