Oh yeah, it is. I wouldn't even try it on your computer - it ran for a good two hours before I got bored on my 3.6Ghz core.
On Wed, Sep 17, 2014 at 5:16 AM, Stephen Lyons <[email protected]> wrote: > Is this still an issue, IIRC there have been changes in the exits area > of the code which may have impacted on this? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1226481 > > Title: > deleteArea() doesn't have good performance > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mudlet/+bug/1226481/+subscriptions > -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1226481 Title: deleteArea() doesn't have good performance Status in Mudlet the MUD client: Confirmed Bug description: On the attached map, deleteArea(255) took 10min+ (not exaggerating) on a 3.6Ghz machine, using latest git. The client locked up during this and was unusable. Is there any way this could be improved? To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1226481/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mudlet-makers Post to : [email protected] Unsubscribe : https://launchpad.net/~mudlet-makers More help : https://help.launchpad.net/ListHelp
