Some objects were not cleaned up when closing the scene. (Did you spawn new GameObjects from OnDestr...

这个警告信息通常出现在Unity编辑器中关闭场景时，表示该场景中的某些游戏对象在销毁时没有被正确清理。这可能是由于在OnDestroy()函数中生成新的游戏对象而导致的。

如果你在OnDestroy()函数中生成了新的游戏对象，Unity无法自动清理这些对象，因为它们不在场景的编辑器层次结构中。为避免这种情况，你可以在OnDestroy()函数中手动销毁这些游戏对象，或者将它们添加到编辑器层次结构中，这样Unity就会自动清理它们。

如果你不确定哪个游戏对象没有被正确清理，可以尝试在Unity编辑器的控制台中查看警告消息，以获得更多信息。

相关问题

Link in the new vma even if an error occurred, so that exit_mmap() can clean up the mess.

In the context of the Linux kernel, the Virtual Memory Area (VMA) is a data structure that describes a range of virtual memory addresses that have a common set of attributes, such as permissions and caching behavior.

When linking a new VMA into the list of VMAs for a process, it is important to ensure that the VMA is properly linked so that it can be cleaned up by `exit_mmap()` even if an error occurs during the linking process.

Here is some sample code that demonstrates how to link a new VMA into the process's VMA list, even if an error occurs:

#include <linux/mm.h>

int insert_vma(struct mm_struct *mm, struct vm_area_struct *vma) {
    int error;
    struct vm_area_struct *prev, *next;

    // Find the correct position to insert the new VMA
    prev = NULL;
    next = mm->mmap;
    while (next && next->vm_start < vma->vm_start) {
        prev = next;
        next = next->vm_next;
    }

    // Link the new VMA into the list
    vma->vm_next = next;
    if (prev) {
        prev->vm_next = vma;
    } else {
        mm->mmap = vma;
    }

    // Defer error checking until exit_mmap()
    error = 0;
    if (error) {
        // An error occurred, but link the VMA anyway
        vma->vm_flags |= VM_ACCOUNT;
    }

    return error;
}

In this code, `insert_vma` inserts a new VMA `vma` into the process's VMA list. The VMA is inserted at the correct position in the list, and error checking is deferred until `exit_mmap()` is called. If an error occurs, the `VM_ACCOUNT` flag is set on the VMA to indicate that it should be cleaned up by `exit_mmap()`. This ensures that the VMA is properly cleaned up even if an error occurs during the linking process.

y hdfs://gzh3master:9000/user/hive/warehouse/stocks could not be cleaned up.

这个错误通常是由于 Hadoop 文件系统（HDFS）权限不足或者目录已经被其他进程锁定导致的。你可以尝试以下解决方案：

1. 检查 HDFS 目录的权限和所有者，确保你有足够的权限来删除该目录。

2. 检查是否有其他进程正在使用该目录，如果是，先停止这些进程，然后再尝试删除该目录。

3. 如果以上两种方法都无法解决问题，可以尝试重启 HDFS 服务，然后再尝试删除该目录。

希望这些解决方案能够帮到你。