YOUR ACCOUNT

Login or Register to post new topics or replies
Rachel Duim
So Called Tortured Artist

Posts: 2498
Filters: 188
Often when exiting the editor (saving or not) FF 4 crashes. If Saving, the save works. I have a crash report with the thread info in a text file if you would like to see it. How should I send it? It does not happen every time, but it is reproducible. Here's my system info.
Rickster

Math meets art meets psychedelia.
  Details E-Mail
Rachel Duim
So Called Tortured Artist

Posts: 2498
Filters: 188
I've attached the crash report as a txt.

[ ff-crash1.txt ]
Math meets art meets psychedelia.
  Details E-Mail
GMM
Moderator
Filter Forge, Inc
Posts: 3491
Thank you but this is an Apple crash report – it contains no useful info for us. Please provide an internal FF log instead: it is located at
/private/tmp/Filter Forge universal.log

Quote
It does not happen every time, but it is reproducible

Looks contradicting to me: an issue is either reproducible, or not reproducible...
  Details E-Mail
Rachel Duim
So Called Tortured Artist

Posts: 2498
Filters: 188
Bad choice of words on my part... in 20 saves or quits from the editor, it would probably crash about 20% of the time, or about 4 out of 20. I did a Safe Mode reboot (which cleans up the disk and internal files etc) then a shutdown. Powered back up, I am testing now. Ok, FF crashed. Can not find any file with that name:
/private/tmp/Filter Forge universal.log
Looked both from the finder (search for files) and as su from the terminal. What now? smile:?:
Math meets art meets psychedelia.
  Details E-Mail
Rachel Duim
So Called Tortured Artist

Posts: 2498
Filters: 188
repost, can't find the universal.log file. see previous.
Rickster
Math meets art meets psychedelia.
  Details E-Mail
GMM
Moderator
Filter Forge, Inc
Posts: 3491
You won't find this file via search, you need to open this folder directly: in Finder, select Go > Go to folder > /private/tmp/
  Details E-Mail
Rachel Duim
So Called Tortured Artist

Posts: 2498
Filters: 188
As I mentioned, also looked for the files as su from the terminal. Just had another crash in FF, here is a pasted listing as super user of /private/tmp/ :

---- start of listing
macbookpro:~ carolhernandez$ su
Password:
sh-3.2# cd /private/tmp
sh-3.2# ls -a
.
..
amt3.log
eyeconnect
launch-AMNLeg
launch-uWteDu
launch-wtNQX2
launchd-184.GhJwbl
launchd-299.in2y9f
launchd-863.6ZgofG
lilo.966
oobelib.log
sperion
swtag.log
totalfinder-uninstaller-overlay-icon.png
sh-3.2#
---- end of listing

As you can see, no log file. I will reboot and continue to investigate.
Rick
Math meets art meets psychedelia.
  Details E-Mail
Rachel Duim
So Called Tortured Artist

Posts: 2498
Filters: 188
Uh, is anybody out there? As I mentioned, there is no Filter Forge universal.log file after an FF crash on my system. The listing of /private/tmp/ is the previous post. How do I proceed?
Math meets art meets psychedelia.
  Details E-Mail
Skybase
2D/3D Generalist

Posts: 4025
Filters: 76
You'd wanna use Console for viewing log files.

Console is found in applications/utilities folder.

I think the User Diagnostic Reports were the key here... buut you wanna make sure that's even the right thing you should be sending to people.
  Details E-Mail
Rachel Duim
So Called Tortured Artist

Posts: 2498
Filters: 188
Did not use Console, but no universal log file exists, so nothing to look at as far as I can tell. Is there something I can get from the Console after the crash that they can use at FF for debugging?
Math meets art meets psychedelia.
  Details E-Mail
Skybase
2D/3D Generalist

Posts: 4025
Filters: 76
It's a log viewer and it's a . You can see almost everything your system is doing. There are also diagnostic reports.

You never have to fumble around with terminal cd-ing all over the private var files where-ever those logs are.
  Details E-Mail
CFandM
ForgeSmith

Posts: 4761
Filters: 266
Here you go...
http://pondini.org/OSX/Logs.html
Stupid things happen to computers for stupid reasons at stupid times!
  Details E-Mail
Rachel Duim
So Called Tortured Artist

Posts: 2498
Filters: 188
Thanks all for the advice. I've done some sys admin work in the past, so I have no trouble finding my way around a UNIX prompt smile:D I could only find 2 logs from the console, 1 is the Apple crash log, FF can't use it (see above). The other log is a spin log from another day, which appears to have nothing to do with the problem. So, I'm stuck.

To restate the problem: When saving or closing the FF editor the program crashes inconsistently. It happens often enough (sometimes 10% of the time, other stretches 40% of the time). The program is properly saved even if it crashes, fortunately.

I can not find any FF logs other than the Apple crash log after FF crashes. I have looked from the Console, command prompt as root, and Finder, including /private/tmp.
----
Minor update: Ran Onyx utility to clean up permissions issues and clean up old system caches etc. It has improved my situation, but... not 100%. It has crashed once in about 20 editor saves/cancels. Still no sign of log files except the Apple crash log.
----
What's next??
Math meets art meets psychedelia.
  Details E-Mail
Skybase
2D/3D Generalist

Posts: 4025
Filters: 76
Did you look under User Diagnostic Reports?

  Details E-Mail
CFandM
ForgeSmith

Posts: 4761
Filters: 266
Well if the reports or logs do not show anything there is one more thing that I can suggest...Kind of an anal thing but sometimes when finding these type of crashes and their reasons you need to be anal to be helpful smile;) smile:)
Figure out at what point FF crashes...Then either write down the steps or remember them....
Then try those steps to see if you can crash FF...
So in other words what filter being used, image size, using quit or just X out of FF. other apps being run at the same time, using stand-alone or plug-in etc......
One way that I approach this is to think like a cop writing down an accident report. How fast the cars were going, which direction were the cars going, which direction the cars were facing on impact, who hit who..etc.....Its all about the details... smile;) smile:)
Stupid things happen to computers for stupid reasons at stupid times!
  Details E-Mail
Rachel Duim
So Called Tortured Artist

Posts: 2498
Filters: 188
Ah, I'm an old hand at this. Yes, I looked under User Diagnostic Reports. The Apple Crash Report is there, as stated earlier, FF can't use this.

Quote
Thank you but this is an Apple crash report – it contains no useful info for us. Please provide an internal FF log instead: it is located at
/private/tmp/Filter Forge universal.log


Nothing special about the crashes. I can boot, open FF, go to the editor, then cancel (with no editing). Any filter. Repeat this over and over, it will crash eventually. The only difference I ever noticed was that it crashes more often IF it is in the process of redrawing the presets after exiting the editor. Unless there is a suggestion by someone @ FF on how to generate a crash report they can use, I'm afraid this is where this will stay.
Rickster
Math meets art meets psychedelia.
  Details E-Mail
CFandM
ForgeSmith

Posts: 4761
Filters: 266
Well I don't work for FF but I am very familiar with FF and reporting bugs and finding them.. smile;) smile:)
I went through that crash text you posted here....I see at thread 15 there are a lot of references to blurs....So I would suggest maybe checking if FF crashes with filters that use a blur component versus filters that don't use blur components....I know there were some issues with the blur and osx... smile;) smile:hammer:
Stupid things happen to computers for stupid reasons at stupid times!
  Details E-Mail
Rachel Duim
So Called Tortured Artist

Posts: 2498
Filters: 188
I can tell you that most of my filters have a blur component... checking... some of my filter have Blur, some don't. Just ran a test, it crashes on filters with or without the blur component. Thanks for the ideas, got any more? An experienced hand is helpful.

The notable thing about the bug is that I can run from a clean boot, run FF, go straight to the editor, do nothing, cancel ( and repeat), and it will eventually crash.

I am probably going to reinstall FF4. I've backed up my system (filters included).

I do have a short term solution. I just purchased the Windows version, a sale is on. I should have that up in a day or 2 smile8)
Math meets art meets psychedelia.
  Details E-Mail
CFandM
ForgeSmith

Posts: 4761
Filters: 266
Re-installing would be helpful....Now here is the tricky anal part.. smile;) smile:)
Sometimes when you get a crash the cause is not so obvious.. Leave FF with the default filters and see if any of those crash FF effects and textures....If they all do then that will be a different issue to figure out....If there is only a couple that do crash FF then figure out which filters crash FF....Now from there figure out what those filters have in common component wise.......I have other ideals but narrowing down the cause is tedious in some cases.....

When you go straight to the editor are you editing a filter or creating a new filter?....
Windows version I can help more with.. smile;) The most recent version of OSX I have is Snow Leopard running on a hackintosh.. smile;) smile:)
Stupid things happen to computers for stupid reasons at stupid times!
  Details E-Mail
Rachel Duim
So Called Tortured Artist

Posts: 2498
Filters: 188
I've just moved my Windows system (4 core screamer) and have installed FF4, will move the filters from my Mac in a minute.

I did a reinstall, but it kept the previous filters (both library and mine). Did not help. I'm always editing an existing filter. I've got OSX 10.9. It's free, but don't do it. Not the best upgrade.

I understand the debugging process well being a programmer as well as an artist, you do a good job explaining the process. I'd love to figure it out, but I've got a life outside of FF.

Honestly, this bug was not the only one, but it is the one that occurs most frequently. The other thing that's not so good: The standalone runs a lot faster than the plugin in PS6. So most of my work has been done in standalone mode. Sometimes I go back and remask in PS. I am looking forward to running in Win7, looks faster already with just the shipped filters.

Thanks,
Rickster
Math meets art meets psychedelia.
  Details E-Mail
Totte
Übernerd

Posts: 1460
Filters: 107
+1 on this...

Process: Filter Forge [30931]
Path: /Applications/Filter Forge 4/Filter Forge.app/Contents/MacOS/Filter Forge
Identifier: com.FilterForge.FilterForge4
Version: 4.0
Code Type: X86 (Native)
Parent Process: launchd [161]
Responsible: Filter Forge [30931]
User ID: 501

Date/Time: 2014-06-08 17:31:06.397 +0200
OS Version: Mac OS X 10.9.3 (13D65)
Report Version: 11
Anonymous UUID: 745E536B-6D22-6A23-5BB4-00B6967C2672


Crashed Thread: 34

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
Assertion failed: (r->shape != NULL), function assert_check_region, file Regions/CGRegion.c, line 28.


Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_malloc.dylib 0x91132afb tiny_malloc_from_free_list + 110
1 libsystem_malloc.dylib 0x911330c8 szone_malloc_should_clear + 283
2 libsystem_malloc.dylib 0x91128b6a szone_malloc + 24
3 libsystem_malloc.dylib 0x9113555b malloc_zone_malloc + 75
4 libsystem_malloc.dylib 0x91135f44 malloc + 52
5 com.apple.CoreFoundation 0x90ab2dbd __CFRunLoopRun + 333
6 com.apple.CoreFoundation 0x90ab29fa CFRunLoopRunSpecific + 394
7 com.apple.CoreFoundation 0x90ab285b CFRunLoopRunInMode + 123
8 com.apple.HIToolbox 0x99c54b5d RunCurrentEventLoopInMode + 259
9 com.apple.HIToolbox 0x99c54777 ReceiveNextEventCommon + 163
10 com.apple.HIToolbox 0x99def936 ReceiveNextEventInMode + 75
11 com.apple.HIToolbox 0x99def99a ReceiveNextEvent + 72
12 com.FilterForge.FilterForge4 0x0071ba6c Controls::ScrollPreviewTask::invoke(XFW::OS::Environment&) + 2538
13 com.FilterForge.FilterForge4 0x00721d8e Controls::FormProcessingTask::invoke(XFW::OS::Environment&) + 68
14 com.FilterForge.FilterForge4 0x0097a065 FFXLib::Round2::get_class_info() const + 1815
15 com.FilterForge.FilterForge4 0x0097a212 FFXLib::Round2::get_class_info() const + 2244
16 com.FilterForge.FilterForge4 0x0071ddca Controls::ScrollPreviewTask::invoke(XFW::OS::Environment&) + 11592
17 com.FilterForge.FilterForge4 0x00073dbc XFW::Events::EventInvokeAdapter<FFX::FileProcessingForm, Controls::KeyboardEventArgs const>::clone_object() const + 3560
18 com.FilterForge.FilterForge4 0x00194091 XFW::Events::EventInvokeAdapter<FFX::LightingSettingsPanel, Controls::MouseWheelEventArgs>::clone_object() const + 17377
19 com.FilterForge.FilterForge4 0x0099b128 XFW::Helpers::CheckFailed::clone_object() const + 3946
20 com.FilterForge.FilterForge4 0x0099c66d XFW::Helpers::CheckFailed::clone_object() const + 9391
21 com.FilterForge.FilterForge4 0x009a075e XFW::Localization::LanguagesStorage::~LanguagesStorage() + 118
22 com.FilterForge.FilterForge4 0x00002346 0x1000 + 4934
- I never expected the Spanish inquisition
  Details E-Mail
Rachel Duim
So Called Tortured Artist

Posts: 2498
Filters: 188
More of an FYI than anything... the crashes on the Mac in FF4 continue. Seems that it might be some of kind of memory issue (leak??). The latest: my new filter Water & Ice on Glass crashes it quite a bit. The only component that is not in my other filters is Refraction. Crashes under a couple of circumstances, exiting/cancelling the editor, double clicking on a preset, but not consistently. Sometimes the slider controls stop working, but I can still enter a number. At this point I quit FF4 and start over. Originally thought that maybe my MacBook Pro had a problem, but no other programs exhibit any issues (Photoshop CS6, Open Office, Firefox, Thunderbird, etc).
Math meets art meets psychedelia.
  Details E-Mail

Join Our Community!

Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!

33,712 Registered Users
+18 new in 30 days!

153,537 Posts
+6 new in 7 days!

15,348 Topics
+72 new in year!

Create an Account

Online Users Last minute:

22 unregistered users.