Hard Lock-up from using Xlist on Xclip Frame

[kickhead70]

Just posting this as an FYI and something to avoid if you can help it, also to let AutoDesk know of the issue, but it's likely pretty uncommon.

I've found that attempting to use Xlist on an Xclip from that existing in an attached Xref will cause the program to lock up and be completely unresponsive. I have tried to wait it out, but after more that 1/2 hour there was no change. Had to use task manager to kill the application.

Scenario:

Dwg-3 has Dwg-2 attached as overlay.

Dwg-2 has Dwg-1 attached as overlay and uses an Xclip rectangle to clip excess content from Dwg-1.

Xclip frame is visible in Dwg-3 via the xref. Using Civil 3d 2014.

While having Dwg-3 open, run Xlist, select the Xclip frame...

[Jay_B]

I'm unable to duplicate the issue in 2014 SP2.

What service pack are you using?

[kickhead70]

I do have SP2 installed. Another aspect is that I commonly lock my xref insertion layers, so that the xclip box would be on a locked layer. I also usually use relative paths to attach xrefs. I this case, one of the drawings attached (say dwg-1) is not relative pathed. Another aspect of it that could be relevant is that I have used dview-twist to orient my view parallel to a driveway on my site.

thanks,

Steve

[Jay_B]

Dview twist = 90 deg.

Xref's attached Relative path

Xref Layer = Locked

Still not seeing anything here.

[kickhead70]

if you're willing, take a look at the 3 drawings attached that mimic my scenario.  These caused a lock up on my end.  If you open Drawing3.dwg, it will have Drawing1.dwg xref'd. the rectangle is a xclip frame from drawing1.dwg. when I run xlist, the results box pops up, but blank, and autocad is stuck.

thanks again!

[kickhead70]

another interesting item just discovered: using "-xlist" gives this... (copied from command line window)

Command: -XLIST
Initializing...
Select nested xref or block object to list:
Usage: (acet-str-format <format> [<arg> ...])

[Jay_B]

I was missing a very important tidbit here.

The Xclip is actually in Drawing1.dwg and you're attempting to select the rectangle representing the

Frame or Xclip limits within Drawing1.dwg via the xref into Drawing3.dwg.

Yes I can get it to show the blank xlist box and freeze.

And the command line displays this if I use the old school -xlist.

Command: -XLIST
Initializing...
Select nested xref or block object to list:
Usage: (acet-str-format <format> [<arg> ...])

But I wonder if the fact that your trying to Xlist an Xclip boundary (which is actually nested) because dwg2 is attachment type xref within dwg1 is pushing things to the limits? The command might not be able to support that operation.

If I xlist normal entities such as the hatch which is in dwg1 the xlist box functions normally as expected.

It also works as expected in my dwg's xlisting xref'd entities so I can't say if this could be considered a bug or not? Other than if it's not a supported command it should return a message indicating so.

[kickhead70]

Thanks for verifying that.  I see where Xlist would not be intended to be able to report a clip frame, but a solid lock up like that is a pretty harsh punishment, that's what was more upsetting to me than the function not working. Do you know how to get the attention of a anyone at AutoDesk to report this to them?

thanks again!

Steve

[Jay_B · Accepted solution]

I'm certainly not making any excuses for AutoDesk but it's a lot like touching a hot stove, once it's happened it likely won't be repeated any time soon, now that you're aware what's causing the pain 🙂

Basically you have two options.

If on Subscription you can file a Support Request and make them aware of the issue.

If you wish to provide direct product feedback to AutoDesk send them a note here.
http://usa.autodesk.com/adsk/servlet/index?siteID=123112&id=1109794

[clindner]

Just an update on this issue (which still exists in 2017, BTW).

This problem can be prevented by a simple edit to the XList.lsp file. 

Open the file and search for this code:

(if kUseDialog (DisplayDialog) (DisplayList))

Replace it with this:

(if sObjectType
  (if kUseDialog (DisplayDialog) (DisplayList))
  (alert "\nUnrecognized object type.")
)

If you prefer not to do the edit yourself, the attached file is updated.

Thanks,

[bobbyk_jr]

 Can confim, this is still an issue in 2017.  Thanks for the fix!

-bk

[Cadguru42]

This just happened to me in C3D 2018. I don't know what the rectangle object was, which is why I tried to do an XLIST on it. It caused the dialog box to open, but it was blank and hitting OK or X wouldn't close the box. I had to force close acad.exe. 

Yet another bug that Autodesk refuses to fix. <sigh>

[clindner]

Cadguru42,

A simple code update will prevent this from happening again. See my post above.

Cheers,

[hdeanNMN6H]

Where in the program files is the xlist .lsp file? Still happening in C3D 2019

[clindner]

---

@hdeanNMN6H wrote:

Where in the program files is the xlist .lsp file? Still happening in C3D 2019

---

Mine was in "C:\program files\autodesk\autocad 2017\express\xlist.lsp"

[rebeccadfreed]

this exact issue came up on my application 

[rebeccadfreed]

this exact issue came up on my application 

[clindner]

---

@rebeccadfreed wrote:

this exact issue came up on my application 

---

@rebeccadfreed ,

Unfortunately, this is still uncorrected by Autodesk,

It is easily fixable, though. Please see my earlier post.

Thanks,

Chris

[mlehmanK7G3Q]

We pay Autodesk not to have to make these fixes ourselves...I'm a civil engineer, not a helpdesk technician...

It's ludicrous that simple bugs like this are reported over and over by users and the OEM can't or won't acknowledge them, much less fix them.

[clindner]

---

@mlehmanK7G3Q wrote:

We pay Autodesk not to have to make these fixes ourselves...I'm a civil engineer, not a helpdesk technician...

It's ludicrous that simple bugs like this are reported over and over by users and the OEM can't or won't acknowledge them, much less fix them.

---

I share the frustration, @mlehmanK7G3Q ! It's a tough spot; we either suffer with it, waiting & pressuring Autodesk to fix it, or fix/patch it ourselves thus giving Autodesk a "pass" so to speak.

But, hey, 2019 has a new "dark theme" that you can use! 😠 #smh