Login
User Name:

Password:



Register

Forgot your password?
void nanny_get_new_race -- comm.c
Mar 13, 2025 7:08 am
By Elwood
IPv6
Jan 25, 2025 10:45 pm
By Samson
mudstrlcpy and mudstrlcat
Jan 18, 2025 5:23 pm
By Samson
I3 and IMC
Jan 17, 2025 9:35 pm
By Samson
AFKMud 2.5.1
Jan 17, 2025 2:22 pm
By Samson
SWFotEFUSS 1.5.3
Author: Various
Submitted by: Samson
SWRFUSS 1.4.3
Author: Various
Submitted by: Samson
SmaugFUSS 1.9.8
Author: Various
Submitted by: Samson
AFKMud 2.5.2
Author: AFKMud Team
Submitted by: Samson
SmaugFUSS 1.9.7
Author: Various
Submitted by: Samson
Users Online
Anthropic, Google

Members: 0
Guests: 7
Stats
Files
Topics
Posts
Members
Newest Member
507
3,812
19,723
597
LydaCawtho

» SmaugMuds » Bugfix Lists » AFKMud Bugfix List » [Bug] Failed object invocatio...
Forum Rules | Mark all | Recent Posts

[Bug] Failed object invocation results in a memory leak
< Newer Topic :: Older Topic > AFKMud 2.01

Pages:<< prev 1 next >>
Post is unread #1 Oct 14, 2007 12:14 pm   
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,707
JoinedJan 1, 2002

 
Bug: Failed object invocation results in a memory leak
Danger: Low - Memory leak under specific conditions
Discovered in: AFKMud 2.01
Found by: Samson
Fixed by: Samson

---

act_wiz.cpp, objinvoke

Locate:
      if( !ch->is_imp(  ) )
      {
         ch->print( "Loading of rare items is restricted to KLs and above on this port.\r\n" );
         return;
      }


Change to:
      if( !ch->is_imp(  ) )
      {
         ch->print( "Loading of rare items is restricted to KLs and above on this port.\r\n" );
         obj->extract(); // It got created, now we need to destroy it.
         return;
      }


Simple oversight. If the multiport functions are enable and someone who is below the admin level tries to load a rare item, they get told they can't do that on the main game port. That object still got generated in memory and was still added to the global object list. But it has not been placed in an inventory or in a room. It is essentially left dangling. Needless to say this results in a memory leak of sorts, even though the object is technically still reachable by the update loops.

Pages:<< prev 1 next >>