This problem was fixed in ver 20171229.17.
This problem occurs when an invalid pointer is extended and data is allocated to the 0xFF area.
consideration to the area filled with 0xFF was insufficient.
I was thinking about only the area filled with 0x00 and the end of the ROM, and I was not considering 0xFF.
1.Extend the class.
2.Specify animation method of added class ID ..
3.Since the pointer is empty in the added class, it is necessary to secure a new area.
4.At this time, designate that 0xFF 0xFF is filled.
5.When alloc data, when new data is alloced from an invalid pointer, it is invalid data and there is no existing termination data.
Therefore, the initialization of the termination data fails.
Data corresponding to that place is used as termination data.
Normally, 0x00 or ROM terminates, but when allocated to the 0xFF area, it becomes 0xFF.
This still does not cause problems.
In addition, a reproduction procedure is necessary.
6.Use up all allocated lists.
For example, after securing two pieces, please enter data for both of them.
7.Reloading the screen causes problems.
Originally,[data 1] [data 2] [term 0x00] should be secured.
Therefore, even if data 1 data 2 is exhausted, there is nothing wrong with it.
However, it failed in (5) to initialize the termination data.
And the allocated area was filled with 0xFF 0xFF as specified in (4).
Therefore, the termination data was 0xFF instead of 0x00.
[data 1] [data 2] [term 0xFF]
Therefore, if data1 data2 is exhausted, the termination data will be gone.