Login
User Name:

Password:



Register
Forgot your password?
Vote for Us!
parse description bug
Dec 15, 2017, 10:08 pm
By Remcon
Couple bugs
Dec 12, 2017, 5:42 pm
By Remcon
Bug in disarm( )
Nov 12, 2017, 6:54 pm
By GatewaySysop
Bug in will_fall( )
Oct 23, 2017, 1:35 am
By GatewaySysop
Bug in do_zap( ), do_brandish( )
Oct 18, 2017, 1:52 pm
By GatewaySysop
LOP 1.45
Author: Remcon
Submitted by: Remcon
LOP Heroes Edition
Author: Vladaar
Submitted by: Vladaar
Heroes sound extras
Author: Vladaar
Submitted by: Vladaar
6Dragons 4.3
Author: Vladaar
Submitted by: Vladaar
Memwatch
Author: Johan Lindh
Submitted by: Vladaar
Users Online
CommonCrawl, Yandex, Yahoo!, DotBot, Sogou

Members: 0
Guests: 5
Stats
Files
Topics
Posts
Members
Newest Member
477
3,706
19,240
608
LAntorcha
Today's Birthdays
There are no member birthdays today.
Related Links
» SmaugMuds.org » 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, 10:14 am
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,639
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 >>