Bug #1134
Memory leak in VNet creation
| Status: | Closed | Start date: | 02/16/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 3.4 - S0 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 3.2 |
Description
VirtualNetworkPool::allocate creates twice vn = new VirtualNetwork(..)
Other pools should be checked
Associated revisions
Bug #1134: Remove double object creation in VirtualNetworkPool::allocate
Bug #1134: Remove double object creation in VirtualNetworkPool::allocate
(cherry picked from commit b177159a3c30e62383c63750ae04e49ab1f623ad)
Bug #1134: Remove double object creation in VirtualNetworkPool::allocate
(cherry picked from commit b177159a3c30e62383c63750ae04e49ab1f623ad)
History
#1
Updated by Carlos Martín over 9 years ago
- Status changed from New to Closed
- Resolution set to fixed
#2
Updated by Ruben S. Montero over 9 years ago
- Target version changed from Release 3.4 to Release 3.4 - S0