File called oobo in trash on every reboot?

Nov 6, 2008 at 5:01pm

File called oobo in trash on every reboot?

Everytime I reboot my Macbook Pro, I get a “Recovered File” in the trash under a folder called MAXMSP-mxt. The file is simply named oobo. It’s not a big deal, just annoying as hell. Any ideas?

#40708
Nov 6, 2008 at 5:13pm

Same here, are you using a demo?
And: i am not annoyed by emptying trash, how comes you are?

:) jrp

#144294
Nov 6, 2008 at 5:15pm

Nope, I have purchased MAX5 a while ago. I just got the new Macbook Pro. Never noticed this on my G4 iBook. I am a crazy man who hates stuff in my trash. If it’s in there, it best be gone!

#144295
Nov 6, 2008 at 5:24pm

ah interesting (write an applescript emptying the trash automatically..?)

OT now but: i was on an Ibook G4/10.4.11 until yesterday (broke down with well-known logic board error – only fan runs…)

So how’s the new MAcbook Pro? Does it behave stabily? i was considering to get one myself, especially as the smaller Macbooks don;t have firewire anymore. Does it run 10.4.11? i don;t need Leopard, really, just sems to suck up CPU…

Thanx in advance, jrp

#144296
Nov 6, 2008 at 5:28pm

Should run Tiger, I use Leopard though. Runs Ableton Live and MAXMSP perfectly. Hardly any CPU usage for what I have been doing. I love it :]

#144297
Nov 6, 2008 at 5:29pm

Since version 4.6, Max has been creating files called oobo in the system temporary folder. Normally these files should be deleted when Max quits, or shortly thereafter, but it’s possible that if the program crashes or you have a permissions problem on your system that the contents of the temporary folder will appear in your trash. It turns out to be fairly hard to write a program to delete a folder on the Mac, and the code we wrote to do so was unreliable, so we decided to chop that code and count on the system to handle it for us. This is equally problematic, as for a certain small number of people, an accumulation of oobo files occurs. I’m not sure why the Mac OS thinks it needs to “save” anything “temporary” by putting it in the trash. I’m just speculating here, but there are a lot of weird things in the Mac OS that are there only to support Microsoft applications. This might be one of them.

Sorry I don’t know more about this. If it is 100% reproducible on the new MBP that would be very helpful in trying to track down the mystery.

David Z.

#144298
Nov 6, 2008 at 5:42pm

I appreciate the response. I will try repairing permissions later today.

#144299
Nov 7, 2008 at 2:33pm

Just to add to this, while testing a standalone we found that every time one of our testers ran the program and then restarted there was a folder in his trash with all the objects used including externals.

This was using Max 5.0.3 at the time though we haven’t tested using a later version.

He is running OS 10.4 whereas I don’t get the problem on my 10.5 machine.

Doesn’t bother us but perhaps this is related in someway?

#144300
Feb 23, 2010 at 8:26pm

I have the same problem,i am currently using the nine month version of max in “snow” system and it started to place this file “oobo”
in my trash after some crashes.It was working perfectly for some months and after an update i did to my mac in java, i started it and for first time max did a “meta synth or something update check” if i am correct because this was very quick and i didn’t catch clearly what was.
My question remains after reading this discussion:is it because i made this update in Java?
Max is working less stable since then.
it seems that the most of the cases that max crashes is when i am trying to open the help file of the “patcher object”.

#144301
Aug 10, 2010 at 8:53pm

Same issue here on my new MBP running Snow. I see this issue’s been around for a while. Has anyone found a solution yet?
Finale 2011 was showing a similar symptom dumping some temp files in trash when reboot. That was easy to remedy by just simply assigning the ‘correct’ temp directory in the program.
Not sure if there’s a similar solution for this ‘oobo’ problem on Max.

#144302

You must be logged in to reply to this topic.