Ongoing crash - how to report?

[Shawn42]

I've got an ongoing crash happening in a one sequence. The backup file has been HUGELY helpful but I want to figure out why I am having this issue. What files (besides the rgbeffects and sequence) do I need to post for someone to be able to diagnose the issue? The crash report?
I have attached those three.

Basically in the middle of sequencing I get a crash report and xlights shuts down. Nothing fancy happening and the sequencing thus far has been standard stuff. I have never had this so I am not sure what I am looking for in order to diagnose. 'Check Sequence' only brings up one minor warning about overlapping.

[flyinverted]

The one place that ALL the developers use is the xLights GIT repository.

I suggest you open a case there and link back to this thread for the files.

https://github.com/smeighan/xLights/issues/

[Gilrock]

This is a crash doing a Paste operation which I'm pretty sure I already fixed a couple days ago.  You need to wait for next release.  It can be prevented by not attempting an invalid paste operation.  One way it's happening is people do a control-c without an effect selected and then they try to paste the garbage.  I was fixing something else last release and accidentally moved a piece of code before the parameter check.

[Shawn42]

Gil,

Got it and thank you. To be clear, what is considered and invalid paste so I can avoid doing this?

[sean]

be sure you first highlight something (like an effect on the sequencer grid) and then type ctl-c.
Gil is saying, doing a ctl-c without first highlighting what you want to copy will create an invalid copy.

The next release will protect against this so it wont be an issue

[Gilrock]

This is a crash doing a Paste operation which I'm pretty sure I already fixed a couple days ago.  You need to wait for next release.  It can be prevented by not attempting an invalid paste operation.  One way it's happening is people do a control-c without an effect selected and then they try to paste the garbage.  I was fixing something else last release and accidentally moved a piece of code before the parameter check.

I highlighted in bold above the example I gave of one way it happens but there are probably other ways to get bad data into the clipboard.  Like you could copy data from notepad or another program and try to paste it in.

[Shawn42]

Got it. Thank you as always gents!