Ok, I've double checked. Officially this isn't a case that the current code was intended to address (i.e. it only fixes the most basic case).

Thanks, I'll see what we can do about this :)

Oh, I found the way to upload the file. The problem is that euler filter doesn't solve the euler rotation jump in Graph Editor. The scene file I've uploaded has a cube with the rotation function curves and they are not continues. Please have a look and make a solution.

how can I attach file?

There is insufficient information here to do anything about this report.

Oh, and I forgot to mention: To increase your framerates, I strongly recommend you to reduce the number of open animation editors per editor to only a single one. Currently you've got all 3 open + the timeline, which does add up :)

This isn't really a bug, as some performance drop is to be expected.

(may be redundant but while browsing my reports from last year, Bastion told me to not re-open tasks myself, and considering I'm not even sure if it's the same thing, I re-closed it )

Wasn't sure if this was supposed to be re-opened, submitted as new, or mentioned as a note but:

https://developer.blender.org/differential/diff/9208/

@Aaron Carlisle (Blendify) here my diff
https://developer.blender.org/differential/diff/9208/

@colin (col-one) welcome! Can you please create a diff and post it on https://developer.blender.org/differential/diff/create/

Hello,
I am new in the blender devel world. To get used to it, I tried to do this task, and it's work. I see there is already a wip on it.
But if it's possible to have some review on my code, it will be very cool. Thanks !

@Joshua Leung (aligorith) will let you handle this, but would say there is no bug here? Mere piling of evaluation work leading to slower FPS, kind of expected…

I finally got around to checking on this report again today.

Without a test file to demonstrate the sitaution where it's "stuck", I can't say for sure what's going on in that case.

This is actually two different problems.
Part 1 (the keyframe-crash) is/was a secondary concern.

The Right-Click Menu says no but the hotkey says crash ^_^

@Joshua Leung (aligorith) is that kind of settings supposed to be animatable at all?

AFAIK, nothing should be touching anything there. Or at least, that particular setting shouldn't be getting cleared explicitly.

@Joshua Leung (aligorith), can you comment something here? :)

okay i understand. But i think there other uesres out here with the same "problem".

@Rombout Versluijs (rombout), the header was done before the documentation, so the only chance is you missed it.
I think there are only two different scenarios here:

1. the user has blender2.78 or previous. In this case he can easily see the bundled version is 0.4 and mismatches the documentation header. The documentation and release changelog state also with extreme clarity what's changed in 0.5 (Please Read: What's new in Rigify 0.5) so if the feature you are looking for is in 0.5 updates list he just grab the 2.79 and goes. As long as he can read english i can't see a real problem.
2. the user has blender2.79 or newer. The problem doesn't exist at all.

that page is irrelevant to the the current version, acknowledge it, just saying. I took me quite some time to fin dout out this is coming for 2.79. How hard is to put 1 line on that page. Perhaps it was changed in recent days. But it was not saying blender 2.79 2 days ago. I now see blender 2.79

@Rombout Versluijs (rombout) is the official rigify wiki page and, as i wrote previously, there's no other one since it documented for the first time in 0.5. Please look further before posting next time. And stop posting here if your question is not relevant to the topic and you already had support.

Sorry but what page are you talking about? I think your talking about inside pages. Go check the link in the addon in lbender and see what info is there

@Rombout Versluijs (rombout), maybe you missed the first lines of the page. There's a header that states the version of the add-on and the blender release.

Thanks! Sorry about the fuzz. But a little text there cant do harm. Know i went searching and searching, when i could have a little piece of text saying "this documentation is for the upcoming 2.79".