2014b and warnings while updating axis

Hi all,

I'm experiencing some strange warnings in 2014b while using any function which adds text to certain axes. The following code seems to create the warning.

figure;
set(gcf, 'DefaultTextUnits', 'Normalized');
loglog(1:10,1:10,'LineWidth',.5)

Below is the warning I'm actually experiencing while using xlabel

Warning: Error updating Axes. Following is the chain of causes of the error:

   Attempt to start an update traversal on a SceneViewer that is already processing an
   update traversal

> In defaulterrorcallback at 12
  In xlabel at 39

Warning: Error updating NumericRuler. Following is the chain of causes of the error:

   Attempt to start an update traversal on a SceneViewer that is already processing an
   update traversal

> In defaulterrorcallback at 12
  In xlabel at 39

When I put a breakpoint in where the warning is issued I can get the following further information

evt.Error

ans = 

    Error with properties:

           ID: 'MATLAB:handle_graphics:exceptions:SceneNode'
      Message: 'Error updating Axes. Following is the chain of causes of the error:
  '
        Cause: [1x1 matlab.graphics.eventdata.Error]
       Object: [1x1 Axes]

evt

evt = 

    ErrorData with properties:

          Error: [1x1 matlab.graphics.eventdata.Error]
         Source: [1x1 JavaCanvas]
      EventName: 'Error'

Does this look like a bug in my code/settings/path somehow, or is it likely to be a Mathworks issue?

[Andrew Joslin]

I get the same error message when trying to access the XLabel or YLabel property of an axes object:

"Error using matlab.graphics.axis.Axes/get Attempt to start an update traversal on a SceneViewer that is already processing an update traversal"

I'm using the Mathworks-approved syntax:

ah = fh.CurrentAxes; xl = ah.XLabel;

The call to fh.CurrentAxes returns a valid Axes object, which is capable of returning XTickLabels and other Axes properties. However, accessing "ah.XLabel" returns the error in quotes above. I also tried get(ah,'XLabel') and xlabel(ah), which produced the same "Attempt to ..." message, albeit with a different stack trace.

Does anybody have an idea what this is?