We have hit a problem that is unique to 2015, regarding erasing entities. It is not unique to our custom entities - it can be achieved with a standard AutoCAD line.
We have a situation in which the user can select our objects, and with the middle grip, move them - standard stuff (GRIP_STRETCH command). These objects are, however, part of a larger assembly and so if the user moves them out of bounds of the larger assembly, they are erased (think of dragging something out of bounds to dump it).
Up until now - from AuoCAD 2007 through to 2013 (not sure about 2014) - this has worked without any problem. In 2015, however, it is now causing the system to come up with the 'Drawing xxxx has a command in progress' --> Cancel / Retry message, and regardless of whether you cancel it or retry, it then crashes fatally (a 0xC0000005 - access violation).
Due to my other problem of not being able to download the symbols for all Autodesk DLLs (see http://forums.autodesk.com/t5/autocad-2013-2014-2015/unable-to-load-important-pdb-files-for-autocad-... I can only tell you that it dies in accore.dll.
If we don't call erase, the crash doesn't happen - but we obviously need to remove that entity somehow. Removing from the database and deleting the now non-DB-resident entity has the same effect - the crash. Even just *calling* erase() on the object - even if we override subErase() and deny the call to the base class (which I believe should not erase it in the first place?) - still causes the crash. Not calling erase() is the only way to stop it.
To simulate this yourselves, create a project and add a reactor derived from AcEditorReactor so that you can have a commandEnded(). During commandEnded(), look for the command being GRIP_STRETCH and then grab and erase any AcDbLine entities in the drawing (it is important not to ask the user to select one, you must grab them yourself). Then start a drawing, add a line, select it to get the grips and move it by its middle grip, triggering that little bit of code - and for us, that causes the crash.
Any suggestions on what is wrong, and how we can fix / overcome this? If we're doing something fundamentally wrong then please let us know.
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")
