QSA的子对象删除问题
我在删除 QSA 引用的对象时遇到一些问题。在构造函数中，我写道：
QSProject * project = {initialization of QSProject}
MyWrapper * wrapper = new MyWrapper; // MyWrapper is QObject's child. It comes without parent here
project->addObject(wrapper);
我在析构函数中写道：
project->clearObjects();
delete project;
delete wrapper;
当我尝试删除包装器时，该代码会导致析构函数执行时出现段错误。
我做了一些研究，我知道：
- QSProject 不会删除他的“子对象”，所以这不是“双重删除”问题
- 如果我不在构造函数中向 QSProject 添加包装器，它会很好地工作。
- 如果我不删除析构函数中的包装器，它会很好地工作（但内存泄漏）。
这是怎么回事？
I've some problems with deleting QSA's referred objects. In constructor, I've wrote:
QSProject * project = {initialization of QSProject}
MyWrapper * wrapper = new MyWrapper; // MyWrapper is QObject's child. It comes without parent here
project->addObject(wrapper);
I've wrote in descructor:
project->clearObjects();
delete project;
delete wrapper;
This code cause to segfault at destructor's execution, exactly -- when I'm trying to delete wrapper.
I've made some research and I know that:
- QSProject doesn't delete his "children objects", so this is not a "double delete" problem
- If I don't add wrapper to QSProject in constructor, it works well.
- If I don't delete wrapper in descructor, it works well (but memory leaks).
What's up?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
首先，我不熟悉 QSA，但考虑到 Qt API 通常如何工作，QSProject 很可能获得该对象的所有权。这意味着 QSProject 正在使用 QObject::setParent() 重新设置对象的父级。
在这种情况下，您将双重删除该对象。
您是否使用 valgrind 等工具验证了在省略删除时实际上正在泄漏内存？
First, I'm not familiar with QSA, but given how the Qt API usually works QSProject is likely taking ownership of the object. This means QSProject is reparenting the object using QObject::setParent().
In which case you are doubly deleting the object.
Have you verified with a tool such as valgrind that you are in fact leaking memory when you omit the delete?