Pale Moon forum

Greetings,
As a long-time PM user I have seen incompatibility issues from time to time and most of them have been resolved but this is the first time I've seen an extension update causing an actual crash of PM so I figured I'd ask and see if anyone else experienced this issue. I have used the YTHD addon for a long time as well, mainly due to it's autoswitching of video quality and I'm currently using 37.0 of said extension. A day or so ago it updated to "37.0.1-signed" (updates fine in FF 37.0.2) but when running the update in the PM add-on window PM (25.3.1 x64) crashes.
While I do realize debugging an entire extension is a pain and not really a job for the PM devs I just wanted to check with other users if this is happening to them as well or if my system is somehow incompatible and if the "-signed" version flag might have anything to do with it.
If nothing else, just letting you know that it does crash.
Thanks.

Link to plugin in question
Mozilla plugin site link

Event Viewer:
Faulting application name: palemoon.exe, version: 25.3.0.5560, time stamp: 0x551065bc
Faulting module name: xul.dll, version: 25.3.0.5560, time stamp: 0x5510651d
Exception code: 0xc0000005
Fault offset: 0x00000000001723c3
Faulting process id: 0x88c
Faulting application start time: 0x01d07eea966bad50
Faulting application path: C:\Program Files\Pale Moon\palemoon.exe
Faulting module path: C:\Program Files\Pale Moon\xul.dll
Report Id: e59fa6e9-eadd-11e4-82e2-10c37b4847c3
Faulting package full name:
Faulting package-relative application ID:

It would crash on me, even when I went to the 36, so it will be a while to see where it doesn't.

Odd, I'm using 37.0 now and it works perfectly. In fact, none of the previous versions have caused any problem whatsoever.
Not sure what happened with this update.

@darkph0rze: can you list the exact set of steps needed to reproduce the crash?

It is Mozilla's fault, thanks to their signed add-ons policy new, Gecko based browsers below 29 experience crashes when the user tries to install a signed add-on.

Moonchild is working already on a fix for this problem, so until further notice, do not install new add-on versions from AMO

And the official bug report at Bugzilla for this topic: https://bugzilla.mozilla.org/show_bug.cgi?id=1158467

@squarefractal Nothing more than going to PMs Tools->Add-Ons and choosing to update extensions.
@Sajadi I figured it had something to do with that -signed thing, thanks! I'll hold off with updates for now. :]
Thanks for all your good work.

Edit for squarefractal:
Updating manually from AMO has the same effect.
http://i.imgur.com/pmiXJwx.jpg