4.014 crashes too much!

Six SIGABRT crashes today:

5: Assertion failed: (r->shape != NULL), function assert_check_region, file Regions/CGRegion.c, line 28.
Originating at FF code:
com.FilterForge.FilterForge4 0x006f551b Controls::ColorPlanePanel::~ColorPlanePanel() + 26147

and
com.FilterForge.FilterForge4 0x00725b20 Controls::ScrollPreviewTask::invoke(XFW::OS::Environment&) + 2538

1: Assertion failed: (shape != NULL), function assert_check_shape, file Regions/shape.c, line 155.
Originating at FF code:
com.FilterForge.FilterForge4 0x00725b20 Controls::ScrollPreviewTask::invoke(XFW::OS::Environment&) + 2538

I can send complete crash logs if you would like them. The crash usually happens on launch but a couple of times it has happened after I have saved a filter.

I am running FF as a stand alone application - photoshop is not involved.

Filter Forge 4.014.36521.36521 Release-10.5 June, 2015 13:36 Professional Edition

Model Name: Mac Pro
Model Identifier: MacPro6,1
Processor Name: 6-Core Intel Xeon E5
Processor Speed: 3.5 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Memory: 32 GB
Boot ROM Version: MP61.0116.B15

AMD FirePro D500:
Chipset Model: AMD FirePro D500
Type: GPU
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Total): 3072 MB
Vendor: ATI (0x1002)
Device ID: 0x679e
Revision ID: 0x0000
ROM Revision: 113-C3861J-687

I hate to say this, but I have been a long time user of FF 4.0xx, and it has crashed a lot of times in my time of using it on OS X 10.9 & 10.10. I've reported a bug which illustrates the problem in the Beta 5 section of the forum:
[crash?] repeated preset clicking crashes FF5
It appears that when many threads are running (and terminating) that some sort of memory allocation issue or "collision" of some kind occurs that crashes FF 4. Although I reported the bug in FF 5 beta, it also occurs in FF 4. Try it. You can also try the technique on other filters, with varying results.

FYI: it crashes a lot on exiting the editor. A workaround. Save the filter with Command-S, then Cancel. It seems to help for me.

Yes, it is somewhat better, especially on issues with file formats (16 bit PNG) that I was seeing in FF 4. FF 5 beta also renders large output (say 8192x8192) better where FF 4 might have crashed. But the fundamental thread/memory issue (leaking memory?) still remains from what I've seen as I've used FF 5 beta.

My 2 cents. I really don't like reporting these things, I know this at a tough time for FF, now deeply into getting version 5 finished. But, I have to call it as I see it. I'm a Mac user of FF...

My take on that: you might try out beta 5, you just have to request a serial number. I think reporting bugs in beta 5 might get more notice at this point, so post your [bug] or [crash] reports in the Beta 5 forum as a new topic. Make sure the bug is reproducible and clearly explain the steps to create the problem & your OS version & the FF program version + any filters/files needed to reproduce the problem. Crash logs are only somewhat helpful.

4.015 Crashes in the morning
crashes in the evening
crashes at supper time.....
choose locate a file... crashes. not even a dump-file is created
install a new filter... crashes sometimes.
Open FF.... crashes sometimes
Reopen FF... doesnt crash.
System Version: OS X 10.11.4 (15E65)
Kernel Version: Darwin 15.4.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Model Name: MacBook Pro
Model Identifier: MacBookPro10,1
Processor Name: Intel Core i7
Processor Speed: 2.7 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 16 GB
Boot ROM Version: MBP101.00EE.B0A

Valp, have you tried FF6 beta? It is completely rewritten in Cocoa.