In designer persona: dragging layers panel out of initial panel group caused complete crash

[4dimage]

OS: Windows 10 Pro for Workstations
Version: 22H2
Build: 19045.2251
Windows Feature Experience Pack 120.2212.4180.0

Publisher 2.0.0

 

I had 2 documents open and switched to Designer persona. There was the inital panel layout with the layers panel on the right side grouped with brushes, QuickFX, styles.

I draged the layers panel out of the group and the whole application instantaniously freezed. A second window appeared in the background.

windows taskbar: "DockAdornerWindow" (Keine Rückmeldung)

Both windows are freezed but the layers panel dialog can stil be draged around with the mouse (lost it's styling, fallback to Windows default).

After forced task shutdown of Publisher and restart with the same 2 documents open, the second attempt does not reproduce the crash. I could drag out the layers panel from the inital group and dock it left hand in it's own column.

 

Procedure:

Drag out the layers panel from it's initial group -> freeze:

 

Second window in the background appears:

 

Taskbar and TaskManager:

 

[NathanC]

Hi @4dimage,

Many thanks for providing detail along with screenshots, following your workflow on both 10/11 has not re-produced this crash/freeze for me yet, i've used two text heavy document and after switching to the designer persona and dragging out the layers panel from it's original position (Same original panel grouping as your screenshot) the app remained functional.

Is this an issue that you're able to replicate since if you were to use two different/blank documents? If not, could you possibly provide me with the two files used in your example? I've provided a dropbox link below for any uploads.

https://www.dropbox.com/request/iyhVcdOfbIsbjHSncUCg

Thanks in advance!

[4dimage]

Hi Nathan,

i couldn't reproduce this crash since then. It seems there where some problems when changing the inital panel layout after install. I rearranged the layout in alle three apps anyway and until now had no similar crashes. Maybe some unhappy coincidence with the new UI system and hardware acceleration. I see this as solved 🙂