Zugg Software :: View topic - [version X to 3.22 pro]14 windows causes layout to corrupt every time

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

This is a very old bug from I don't remember when, but if you save a session layout with 14 or more windows in any combination of the DB module, the mapper, or Window objects (#window, #makewindow, etc) it will corrupt the next time you open the session. There may or may not be other "core" windows affecting this, but it does not seem as if the Package Editor, Debugger, or the mapper's supporting windows (Room Properties, Find, etc) do.

1)open CMud
2)open/create a new session in offline mode
3)create/make visible 14 windows (12, if you're going to use both the mapper and the DB module)

My specific layout is one capture window docked to the bottom screen border, three windows docked in vertically-tiled format (not tabbed) to the right of the main window, two windows docked in vertically-tiled format to the top of the main window, two windows docked in a horizontally-tiled format to the top of a floating window, and 5 other single floating windows (3 capture windows plus mapper and DB module). The main toolbar is unchecked and all the docked windows have no captions displayed. While it doesn't matter for this procedure, because I'm out of screenspace all six of the floating windows are minimized and moved out of the way.

4)save the layout
5)close the session

At this point, everything should appear to operate as per normal.

6)reopen the session in offline mode

Here the layout should have corrupted into unplayability. I've noticed entire duplication of the layout within a single window, and the main window's text area and commandline go away completely every time.

7)close the session via the File|Close All menu

This closes the session and brings up the Sessions window, but around the time that the Sessions window gets redisplayed an AV error occurs. Presumably due to the corrupted layout that's trying to be saved.

This corruption does not occur at all when there are 13 windows and CMud seems to get really stable in this range, but it doesn't appear to matter one bit which 13 windows you use. At any rate, this situation occurs both before and after a full export, layout reset, and fresh installation so I don't know what more I can do to guarantee other points of corruption didn't slip by me.

Posted: Tue Jul 06, 2010 11:17 pm

I just tried it with 15 tabed child windows (just ran #WINDOW win1, #WINDOW win2,....#WINDOW win15 on the command line). Closed CMUD and reopened the session and it was still fine.

So it looks like the issue is more than just the number of windows involved. Can you play with this to see if you can pin down exactly what starts causing this to happen? Start with a new session and the above procedure to create 15 windows and then see if you can find the docking arrangement that fails.