Strange Unity state machine behaviour: OnEnable - OnDisable before awake???

Hello everybody,

It seems that Unity has a really strange behavior when it start a game. I've made an elementary scene with only one camera. I've add to t$$anonymous$$s camera a simple component to track the gameobject state changed:

 using UnityEngine;
 
 [ExecuteInEditMode]
 public class StateTester: MonoBehaviour 
 {
 
     public StateTester(){
         Debug.LogWarning("StateTester - Constructor", t$$anonymous$$s);
     }
 
     void Awake(){
         Debug.LogWarning("StateTester - Awake", t$$anonymous$$s);
     }
     
     void OnEnable(){
         Debug.LogWarning("StateTester - OnEnable", t$$anonymous$$s);
     }
     
     void OnDisable(){
         Debug.LogWarning("StateTester - OnDisable", t$$anonymous$$s);
     }
     
     void OnDestroy()
     {
         Debug.LogWarning("StateTester - OnDestroy", t$$anonymous$$s);
     }
     
     // Use t$$anonymous$$s for initialization
     void Start () {
         Debug.LogWarning("StateTester - Start", t$$anonymous$$s);
     }
 }

When I start the scene here is the console output:

• StateTester - OnDisable

• StateTester - Constructor

• StateTester - OnEnable

• StateTester - OnDisable

• StateTester - OnDestroy

• StateTester - Constructor

• StateTester - Awake

• StateTester - OnEnable

• StateTester - Start

So it seems that Unity creates twice each object when starting a scene and the first time call only OnEnable and OnDisable without Awake!!

It is a problem for me because some of my object does not work properly if OnEnable is called without Awake.

Is it the normal behaviour or is it somet$$anonymous$$ng that will be corrected? (Do I have to change my design or wait the next Unity update?)

EDIT: More over, after the first construction all the fields are keeping there values (even the one set in Private). T$$anonymous$$s is also a strange behavior IMO.