Custom filter disabled after approximatively 45 minutes

Question

I am developping a filter to render equations in nodes as images from LaTeX code using mathtex library ( http://www.forkosh.com/mathtex.html ).

The filter works quite well, my filter is active, the content is filtered, the node is cached using Boost and the HTML file is containing teh filtered HTML code.

BUT : after several minutes (arround 45 minutes) my filter is disabled (not visible in the input format adminpage, see below) despite that the module is still activated in the module page and the content is not filtered anymore. BUT : when I desactivate/reactivate the modules, OR when I delete all caches, the filter is reactivated, the content is filtered again. And approximatively 45 minutes after it's not filtered anymore.

I try to do the same filter but using the Custom Filters module and I had the same behavior.

I supposed that the cron job had an influence, but content become not filtered BEFORE cron is executed (every hours).

Someone has an idea from where does the problem can come from ?

I'm running : Drupal 7.23 using lots of modules : http://sites.uclouvain.be/selt/files/selt-modules.txt

Some captures to illustrate :

Content not filtered, as after approximately 45 minutes :

Content filtered, as after cache flushing or de/reactivation of module :

Administrative page for format "Full HTML" showing activated mathtex filter :

Administrative page for format "Full HTML" not showing filter :

Answer 1

After several tests and investigations, the culprit was the distant MySQL server which had a too short wait_timout. During cache refreshing operations the server used to go away before filters beeing applyed, leading to caching unfiltered pages. Using a MySQL server with no wait_timeout has solved this problem, without changing any setting elsewhere.

Answer 2

Suggestions to debug:

1. Simplify the setup -- limit your installation to a simple, fresh drupal with only your filter module. No unknown influences, to pinpoint the flaw.
2. If you suspect cron -- turn it off and wait 60 minutes.

But this is individual support. No other user might ever benefit from your very individual problem. It is not a good fit for a public question on stackexchange.