I cannot see this in 6.1. on windows but in the development branch on linux. The axes in the second window are shifted in y-direction. If I grab the second window with the mouse and move it around, the content is then updated correctly:

close all;
hax = axes();
close all;
hax = axes();

If I write the bounding box values in update_camera() before and after moving the figure into a warning message, I see the following:

Plot is displaced in y-direction:
bb0: 72.800000 bb1: 33.825000 bb2: 434.00000000 bb3: 367.565000

After moving around:
bb0: 72.800000 bb1: 31.500000 bb2: 434.00000000 bb3: 342.300000

If I insert a pause time after the second "close all" statement, the problem disappears. It looks to me that this happens if a figure is drawn in a very small moment after another figure is closed by "close all".

The viewport setting in gl-render seems to be correct.

The question is what does a "close all" statement has to do with get_boundingbox()?

If I set in preferences option fusion for Style, I do not see x label on the figure (as you can see on the last posted screenshot, on the right is a script that is executed). I have tested on 4 machines and all of them have the same behavior.

comment #9:

> Do you mean undocking the editor?  Also in this case no luck in reproducing 🤔

Thank you for your responses.

I wrote "on first of multiple figures" based on the first script I have submitted. I have tested with this script on multiple Win10 machines and all have the same bug, I was thinking what could be different and all of them have fusion selected for Style. Currently, I think that this style is somehow the source of the problem, can you test with this style and the second script?

Also here on a Octave 6.1.0 on Windows 10 20H2 machine.  Is your (secondary?) display too small or has a fancy resolution?

I also do not understand your script.  You say "on first of multiple figures", but it stops on the second figure.  I also checked the first one, but still not reproducible.

I cannot reproduce with the second script either.

Actually, it is not reproducible by this script every time, I have to find a better example. Thank you for checking.

comment #1:

> Works for me with Octave 6.1.0 on Windows 10 20H2.

In the attached picture you can see results after running script multiple_figure_bug.m (also attached). As you can see, figure 1 has some kind of problem, and the x label is not visible (the wrong position of the plot inside the figure window) while the rest of the figures are as they should be. If you move the whole figure everything becomes as expected.