 Hi, I am the batch manager from Cloud, and I talk about the challenge of teamwork. It was part of a team effort, so it's going to be coming out in the future. Say thanks to the team for making this teamwork possible. So, what was this teamwork expectation about having teamwork in the challenge in the next session? The major problem was the life cycle of the team, which is conventionally dramatic. From the perspective we used these properties, like the graphic URL, which accepted a string attribute and this string attribute was a URL to add an internal or external URL. So, the graph we have in external URL like HTTP or file, this is not much of a problem, but we used also these internal URLs, which were just classes, strings, and this is sketched like this. For example, we have the sum, this bar, this object, and that sum, XID. And this XID that represented inside the double or lower level set, one graphic object, or image itself, each was sold to the telephone. The IDing was stored inside this graphic edge. I have a little bit of a diagram here, so the total and some sets of graphic URLs and this is all the height where the image itself is stored. This is the graphic object, and this graphic object manager had to import a string ID and store the graphic object inside the graphic edge. What can happen here is that there is no way to add if the graphic is still used. Can it go away? If we have a graphic, we don't know if it's still used or not. But we have a problem. We actually don't know if we have this information. So, it's about something that we present in copying or exterior sections, creation of the graphics, or we just proceed and it is stored inside the double. The result is the user's next type of workman who doesn't have images anymore. We have a graphic object which is a lot safer to use. We have an object, a graphic object that we don't know, and it can just store how many times it is used, and there is no string kind of power going in. We release the memory in the end, but it's still valid. Interestingly, the power goes away. If you pay this release money, it means that we have to change all the cinema properties to use this reference counter to change these cases. It's ex-gaping. And then, after I was one of these, I had to rework the memory. The third one was the cannibalities. If you are thinking about those differences in the behavior, each one would be internal experiment. Actually, you can still save these if you are, if you save it, if you add it to the graphic, you go there. But if you want to get something, it's probably going to be internal experiment. I love that it's possible to store that image if it's not used to release the story and take out the memory. We have to see how much memory, curiously, we saw it already. We just get it in a six-circuit memory. It's just one image, it's not a random slide. We try to get it to be kind of hyper-inducing. The third thing, I don't even show you what it's done, but it's much easier than it seems like it's just one image. It's useful. All these were written in journals. Some of them, but it wasn't. It's there for writers. I'm probably the one who wrote the book. It's a group of bloggers. All these things are in the graphic, especially for navigation itself, which is connected to your smartphone. So one idea is here, it's here. It costs less than a minute. It's also read with us. It's in the world of simulation.