Adding a post-processor script crashes slic3r

Important infos first:
Win 10 Home 64Bit
Slic3r version is 1.2.9.41
Python version is 3.6

Unfortunately the current slicing and postprocessing contains a lot of instances where the valve (printing with a pneumatic system) will not close when crossing borders or moving to another point (besides while printing) which adds a lot of unwanted lines in the model.

I wrote a postprocessing script that tackles this problem. But when I add it in the print settings (there is already a postprocessing script in there which is being used successfully) and save the changes slic3r crashes.
And until I remove the modified Ini from AppData/Roaming/Slic3r/print/modified.ini it won't start either (it shortly appears in the task manager but does not exceed 82MB of RAM before it just vanishes).

Does anyone have an idea why that is the case?

Do you need my postprocessing script?

Glad for every help I can find.

Iphark

Edit:
I just noticed that any change made to the post-processing part leads to a crash of slic3r (e.g. adding or removing a script). So I don't think it has to do with my script.

Edit2:
Since I had one postprocessing script in place that was accepted and working I thought I might just modify it to include the feature I want. Turns out that Slic3r fully ignores the postprocessing script now. After changing the script back into it's original form it is still ignored.

THIS IS DRIVING ME CRAZY.

Edited 2 time(s). Last edit at 07/06/2017 09:06AM by iphark.

Which slic3r version do you use? There are Prusa-versions that are much more stable than the 1.19 "stable"

I see the same crashes everytime I try to change the nozzle diameter in the printer-settings. The only way it works, is to use the "default" profile* and make all changes at once and then save it under a new name.
*( in some Slic3r versions, the default-profiles are hidden and you have to enable " show default settings " in the preferences)

Edited 1 time(s). Last edit at 07/07/2017 02:04AM by o_lampe.

hey o_lampe!

Sorry for the late (nearly 2 months) response.

I used several versions. The older versions are crashing just as I described it, the newer versions ignore the postprocessing script.

I think by now that the reason for this behavior lies in the script. If it contains a bug that raises an error and/or has the wrong header (it works fine for me when I use #!usr/bin/python) the old versions will crash while the new versions will just ignore the postprocessing script.

I don't know which behavior I find more frustrating, but yea, it is what it is.