These messages come from when the global destruction of objects happens. The global destruction does not respect the usual order of object destruction anymore, and in your case, this means that sometimes there are Javascript proxy objects still alive while the bridge to Firefox has gone down already.

I told you on StackOverflow to undef $mech. If that doesn't solve your problems, maybe you keep other references into Firefox. You need to break these references before starting global destruction as well.

Update: It seems that you're creating a WWW::Mechanize::Firefox object over and over again in a loop. Most likely, you'll be better off by creating your object outside of your loop - at least that should be faster as the initialization within Firefox then only needs to happen once.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.