fixed memory leak I introduced
Accidentally introducing a circular reference in a MARC::Record object does not lead to goodness, particularly if you export lots and lots of them. Signed-off-by: Joshua Ferraro <jmf@liblime.com>
This commit is contained in:
parent
cfea172544
commit
e2c1f11715
|
|
@ -377,7 +377,8 @@ sub fix_biblio_ids {
|
|||
# FIXME - it is essential to ensure that the biblionumber is present,
|
||||
# otherwise, Zebra will choke on the record. However, this
|
||||
# logic belongs in the relevant C4::Biblio APIs.
|
||||
my ($marc, $biblionumber) = @_;
|
||||
my $marc = shift;
|
||||
my $biblionumber = shift;
|
||||
my $biblioitemnumber;
|
||||
if (@_) {
|
||||
$biblioitemnumber = shift;
|
||||
|
|
|
|||
Loading…
Reference in New Issue