diff options
author | jan iversen <jani@documentfoundation.org> | 2015-11-04 18:06:29 +0100 |
---|---|---|
committer | Stephan Bergmann <sbergman@redhat.com> | 2015-11-04 20:27:21 +0100 |
commit | 5a29db7a9945c4cd095799451a6c563d5aeeed57 (patch) | |
tree | 3cc98c80ce8a40d5456091ee3225cfa724334821 /qadevOOo | |
parent | 327ed70fa568c0ea3944a5c714479dca03d5f3d5 (diff) |
Solved CID 1326472, 1326473, 1326474
Coverity requires that allocated objects (use of new)
are directly release, by foo = null;
The gc will do this automatically at some point in time,
so this will simply release the resource a bit earlier,
which can save problems if the function is called in a tight
loop.
Updated to add close() before clearing the variable, this would
normally be done by gc, but now a bit earlier. The assignment to
null is not needed specifically, but Coverity calls it a leak if
not assigned.
Forgot .close();
Change-Id: Id273e7f36778c1691b260d28e741c6e32148c9d9
Diffstat (limited to 'qadevOOo')
0 files changed, 0 insertions, 0 deletions