mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

Sorry for the huge log, didn't realise it was that big. Deleting area
255 took 425.933s on Mudlet 2.1 and is still running 3s/room on 3.0 - I
think we can consider this a regression.

** Changed in: mudlet
    Milestone: None => 3.0

-- 
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