Crash when moving phonemes

[craftylag]

2019.27 started around .23 kept thinking it would go a way! Wrong.  Yes it is something I am doing and yes I am an idiot. Not smart etc.  When extending like etc as soon as I stop movement it crashes.
2019-06-05 16:39:49,908 6828 log_base [INFO] Log4CPP config read from xlights.windows.properties.
2019-06-05 16:39:49,908 6828 log_base [INFO]      : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,908 6828 log_base [INFO]     log_base : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,908 6828 log_base [INFO]     log_conversion : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,908 6828 log_base [INFO]     log_generatecustommodel : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,908 6828 log_base [INFO]     log_jobpool : ALERT CRIT EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,908 6828 log_base [INFO]     log_opengl : ALERT CRIT EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,908 6828 log_base [INFO]     log_opengl_trace : ALERT CRIT EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,908 6828 log_base [INFO]     log_pianodata : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,908 6828 log_base [INFO]     log_prepcustommodel : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,908 6828 log_base [INFO]     log_render_log : ALERT CRIT EMERG ERROR FATAL NOTICE WARN
2019-06-05 16:39:49,908 6828 log_base [INFO]     log_timer : ALERT CRIT EMERG ERROR FATAL WARN
2019-06-05 16:39:49,908 6828 log_base [INFO] ******* XLights main function executing.
2019-06-05 16:39:49,908 6828 log_base [INFO] Main: Starting wxWidgets ...
2019-06-05 16:39:49,911 6828 log_base [INFO] Start Time: 2019-05-05_16-39-49-463.
2019-06-05 16:39:49,911 6828 log_base [INFO] Log4CPP config read from xlights.windows.properties.
2019-06-05 16:39:49,911 6828 log_base [INFO]      : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,911 6828 log_base [INFO]     log_base : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,911 6828 log_base [INFO]     log_conversion : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,911 6828 log_base [INFO]     log_generatecustommodel : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,911 6828 log_base [INFO]     log_jobpool : ALERT CRIT EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,911 6828 log_base [INFO]     log_opengl : ALERT CRIT EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,911 6828 log_base [INFO]     log_opengl_trace : ALERT CRIT EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,911 6828 log_base [INFO]     log_pianodata : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,911 6828 log_base [INFO]     log_prepcustommodel : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN
2019-06-05 16:39:49,911 6828 log_base [INFO]     log_render_log : ALERT CRIT EMERG ERROR FATAL NOTICE WARN
2019-06-05 16:39:49,911 6828 log_base [INFO]     log_timer : ALERT CRIT EMERG ERROR FATAL WARN
2019-06-05 16:39:49,911 6828 log_base [INFO] ******* OnInit: XLights started.
2019-06-05 16:39:49,911 6828 log_base [INFO] Version: 2019.27
2019-06

[Gilrock]

So that part of the log you posted doesn't contain any errors that is just the normal startup messages.  I know it might look like errors with the words CRIT DEBUG EMERG but what each of those lines is showing are the debug levels set for each module type in log4cpp.  So not saying you didn't crash just that the log you posted doesn't contain the crash.  It would be best to open xLights and do a Tools -> Package Log Files and then post that zip file it creates.

[craftylag]

File

[Gilrock]

So I don't see any signs of a crash in that log.  Just saying it crashed isn't really specific enough because it could 1) crash and display the debug crash window allowing you to save the crash zip file 2) the app just freezes or 3) the app just disappears.

[craftylag]

Yes you're probably right it seems as it just closes down. Tried to video but as soon as I stopped recording it disappeared.

[Gilrock]

So for a crash like that the probably to fix it is low unless you have a repeatable scenario.  If so you can Package Sequence and tell us the instructions to reproduce it.

[craftylag]

The problem has been there for a while after I think .22 or .23 It does happen with just about any sequence after I copy and paste phonemes. Not sure what I have done to cause the problem. Will try different sequences and see for sure and package one and send.

[craftylag]

Phonemes dropping. Since this is a singing face close group didn't want others to see this file. Working in the 1:42 area with the word begun. Where the notes change trying to add phoneme to give the mouth some movement.  After you see file please remove file

[Gilrock]

Yeah I don't get what you mean.  Around 1:42 the word begun there is no empty space to add a phoneme.  But I shrank a couple and pasted a new ones in just fine.  What do you mean by "Phoneme dropping"?  There is no way to "drop" phonemes that I know of.  You can copy one and then paste it somewhere else and then resize or change it.  I did that all over no problem.

By the way I have no privileges to delete your attachment.

[craftylag]

you said that xlights wasn't giving an crash error so I change the phoneme crashing to phoneme dropping.If you resize the phoneme and it didn't drop( crash ) then I will try installing a new xlight file. I most have a corrupt file of some kind, Thanks

[Gilrock]

Phoneme's don't crash or drop....the program does.