305690 - [Win32] Attempt to free unreferenced scalar in checksetup and post_bug

Status: RESOLVED WORKSFORME

(Bugzilla :: Installation & Upgrading, defect)

Description

[Cédric Caron]

I receive the folowing error when running checksetup.pl

[Wed Aug 24 01:29:19 2005] checksetup.pl: Attempt to free unreferenced scalar: 
SV 0x351359c, Perl interpreter: 0x15d4094 at 
C:\Inetpub\Orchid\Bugs\checksetup.pl line 4016.

Line 4016: AddGroup('tweakparams', 'Can tweak operating parameters');

Comment 1

[Cédric Caron]

The last lines displazed before the error...

Populating duplicates table...
Setting any 'other' op_sys to 'Other'...
Updating column title in table whine_queries ...
Old: varchar(128) NOT NULL
New: varchar(128) NOT NULL DEFAULT ''

Comment 2

[Max Kanat-Alexander]

What version of perl are you using?

Comment 3

[Cédric Caron]

ActivePerl 5.8.7 build 813

Comment 4

[:glob ✱]

confirming.

DBI v1.48, DBD::mysql v2.9008, ActivePerl 5.8.7 build 813

Populating duplicates table...
Creating duplicates directory...
Setting any 'other' op_sys to 'Other'...
Updating column title in table whine_queries ...
Old: varchar(128) NOT NULL
New: varchar(128) NOT NULL DEFAULT ''
[Thu Aug 25 08:47:14 2005] checksetup.pl: Attempt to free unreferenced scalar:
SV 0x2c12110, Perl interpreter: 0x224214 at checksetu
p.pl line 4002.
Adding a new user setting called 'csv_colsepchar'

Comment 5

[Max Kanat-Alexander]

Why do we keep seeing things like this (we saw that selectall_hashref thing,
too)? It seems like something is broken in ActiveState's DBI or DBD::mysql.

Anyhow, I have no idea what to do about this. I hope Byron has some idea. :-)

Comment 6

[:glob ✱]

note the error happens after the change is made.
re-running checksetup results in no errors.

we may have to kludge this one.

Comment 7

[Max Kanat-Alexander]

*** Bug 354085 has been marked as a duplicate of this bug. ***

Comment 8

[:glob ✱]

i also get an error every time i post a bug :(

[Thu Oct 5 21:55:53 2006] post_bug.cgi: Attempt to free unreferenced scalar: SV 0x291b6c4, Perl interpreter: 0x224454 at Bugzilla/DB.pm line 973.

Comment 9

[Max Kanat-Alexander]

(In reply to comment #8)
> [Thu Oct 5 21:55:53 2006] post_bug.cgi: Attempt to free unreferenced scalar: SV
> 0x291b6c4, Perl interpreter: 0x224454 at Bugzilla/DB.pm line 973.

  Hrm. Okay. What's line 973 on your installation, in DB.pm?

Comment 10

[:glob ✱]

it's the last line of _bz_real_schema:

    return $self->{private_real_schema};

Comment 11

[:glob ✱]

oh, the bug is still created without issue.

Comment 12

[:glob ✱]

i'm running DBI 1.52 and DBD-mysql 3.0007

Comment 13

[Marc Schumann [:Wurblzap]]

I'm seeing this with DBI 1.50 and DBD::mysql 3.0002.

Comment 14

[Max Kanat-Alexander]

I can't necessarily mark this as a blocker until we have some sort of root cause. That is, it's possible we could come up with something and say, "Well, we're not going to fix that, time to complain to ActiveState." So let's see what's causing it, and then request blocking again.

Comment 15

[Colin Ogilvie [:cso]]

I also see this as:

Attempt to free unreferenced scalar: SV 0x4d2f548, Perl Interpreter: 0x23413c at Bugzilla/User.pm line 1475, <STDIN> chunk 5.


Attempt to free unreferenced scalar: SV 0x4d2ebdc, Perl Interpreter: 0x23413c at Bugzilla/User.pm line 1513, <STDIN> chunk 5.

Comment 16

[Max Kanat-Alexander]

*** Bug 358172 has been marked as a duplicate of this bug. ***

Comment 17

[:glob ✱]

> Bug 358177 Comment 0
> A brief investigation led to _create_token() in Token.pm. It seems that the
> calls to bz_lock_tables() and bz_unlock_tables() are responsible. The next line
> in the source just is blamed for it.

disabling those functions doesn't resolve the issue (in post_bug).
the same error occurs during checksetup, so it isn't table locking that's the cause.

my bet goes with the schema stuff.  dbi only started crashing with the new DB tier.

Comment 18

[Max Kanat-Alexander]

I've reported this bug to ActiveState:

http://bugs.activestate.com/show_bug.cgi?id=57328

Comment 19

[Norbert Kintzler]

I had the same problem on post_bug.cgi with ActivePerl 813, DBI 1.42, DBD::mysql 3.0002.

After I upgraded ActivePerl to current 820 with DBI 1.52-r1 and DBD::mysql 4.0003 the message does not seem to appear anymore. So it might be resolved although the Bug at ActiveState is still open (unconfirmed).

Comment 20

[Frédéric Buclin]

I haven't seen this message for ages, so probably this is fixed either by newer versions of ActivePerl or by DBD::mysql 4.00, which is now our minimum requirement.