Filebot crashes on launch

All your suggestions, requests and ideas for future development
Post Reply
lamateur
Posts: 2
Joined: 12 Sep 2015, 12:09

Filebot crashes on launch

Post by lamateur »

Hello !

I've just bought Filebot on mac app store and installed it. On launch, the app window starts but there's another window called "getting started". This one loads for 2 seconds and i've an error message

"Fimlebot quit unexpectedly"

I use a macbook pro mid 2012 with OSX v10.9.5

More details of this error message :

Process: FileBotAppLauncher [1776]
Path: /Applications/FileBot.app/Contents/MacOS/FileBotAppLauncher
Identifier: net.filebot.FileBot
Version: 4.6 (3028)
App Item ID: 905384638
App External ID: 812494792
Code Type: X86-64 (Native)
Parent Process: launchd [159]
Responsible: FileBotAppLauncher [1776]
User ID: 501

Date/Time: 2015-09-12 14:05:55.618 +0200
OS Version: Mac OS X 10.9.5 (13F34)
Report Version: 11
Anonymous UUID:

Crashed Thread: 0 AppKit Thread Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

VM Regions Near 0:
-->
__TEXT 000000010e4d2000-000000010e4d6000 [ 16K] r-x/rwx SM=COW /Applications/FileBot.app/Contents/MacOS/FileBotAppLauncher

Application Specific Information:
abort() called

Thread 0 Crashed:: AppKit Thread Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff89b36866 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff8182335c pthread_kill + 92
2 libsystem_c.dylib 0x00007fff8c1e1b1a abort + 125
3 libjvm.dylib 0x000000011022e22f os::abort(bool) + 25
4 libjvm.dylib 0x000000011034ec8c VMError::report_and_die() + 2250
5 libjvm.dylib 0x000000011022fe5a JVM_handle_bsd_signal + 1131
6 libjvm.dylib 0x000000011022c137 signalHandler(int, __siginfo*, void*) + 47
7 libsystem_platform.dylib 0x00007fff88b305aa _sigtramp + 26
8 libjfxwebkit.dylib 0x000000013a7db929 0x139d0a000 + 11344169
9 libjfxwebkit.dylib 0x000000013a6ae5a0 0x139d0a000 + 10110368
10 libjfxwebkit.dylib 0x000000013a6ce041 0x139d0a000 + 10240065
11 libjfxwebkit.dylib 0x000000013a6dcedb 0x139d0a000 + 10301147
12 libjfxwebkit.dylib 0x000000013a6d4fe2 0x139d0a000 + 10268642
13 libjfxwebkit.dylib 0x000000013a6d93df 0x139d0a000 + 10286047
14 libjfxwebkit.dylib 0x000000013a6d9e57 0x139d0a000 + 10288727
15 libjfxwebkit.dylib 0x000000013a6db5c4 0x139d0a000 + 10294724
16 libjfxwebkit.dylib 0x000000013a6dbd80 0x139d0a000 + 10296704
17 libjfxwebkit.dylib 0x000000013a6c0871 0x139d0a000 + 10184817
18 libjfxwebkit.dylib 0x000000013a6c0172 0x139d0a000 + 10183026
19 libjfxwebkit.dylib 0x000000013a6be3b0 0x139d0a000 + 10175408
20 libjfxwebkit.dylib 0x000000013a6bf798 0x139d0a000 + 10180504
21 libjfxwebkit.dylib 0x000000013a6c088b 0x139d0a000 + 10184843
22 libjfxwebkit.dylib 0x000000013a6c0172 0x139d0a000 + 10183026
23 libjfxwebkit.dylib 0x000000013a6be3b0 0x139d0a000 + 10175408
24 libjfxwebkit.dylib 0x000000013a6bf798 0x139d0a000 + 10180504
25 libjfxwebkit.dylib 0x000000013a6c088b 0x139d0a000 + 10184843
26 libjfxwebkit.dylib 0x000000013a6c0172 0x139d0a000 + 10183026
27 libjfxwebkit.dylib 0x000000013a7ca6aa 0x139d0a000 + 11273898
28 libjfxwebkit.dylib 0x000000013a5ad684 0x139d0a000 + 9057924
29 libjfxwebkit.dylib 0x000000013a24987d 0x139d0a000 + 5503101
30 libjfxwebkit.dylib 0x000000013a529921 0x139d0a000 + 8517921
31 libjfxwebkit.dylib 0x000000013a511242 0x139d0a000 + 8417858
32 libjfxwebkit.dylib 0x000000013a54b64e 0x139d0a000 + 8656462
33 libjfxwebkit.dylib 0x000000013a54adbd 0x139d0a000 + 8654269
34 ??? 0x0000000110eb3954 0 + 4578818388
35 ??? 0x0000000110ea5c4d 0 + 4578761805
36 ??? 0x0000000110ea5c4d 0 + 4578761805
37 ??? 0x0000000110ea5c4d 0 + 4578761805
38 ??? 0x0000000110ea5c92 0 + 4578761874
39 ??? 0x0000000110ea59d0 0 + 4578761168
40 ??? 0x0000000110e9e7a7 0 + 4578731943
41 libjvm.dylib 0x00000001100a032a JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*) + 1710
42 libjvm.dylib 0x00000001100f8818 JVM_DoPrivileged + 1208
43 ??? 0x00000001112a1155 0 + 4582936917
44 ??? 0x0000000110ea59d0 0 + 4578761168
45 ??? 0x0000000110ea5c4d 0 + 4578761805
46 ??? 0x0000000110ea5c92 0 + 4578761874
47 ??? 0x0000000110e9e7a7 0 + 4578731943
48 libjvm.dylib 0x00000001100a032a JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*) + 1710
49 libjvm.dylib 0x00000001100d6de6 jni_invoke_nonstatic(JNIEnv_*, JavaValue*, _jobject*, JNICallType, _jmethodID*, JNI_ArgumentPusher*, Thread*) + 773
50 libjvm.dylib 0x00000001100c95a1 jni_CallVoidMethod + 363
51 libglass.dylib 0x00000001394b0493 -[GlassRunnable run] + 163
52 com.apple.Foundation 0x00007fff8394f7ce __NSThreadPerformPerform + 229
53 com.apple.CoreFoundation 0x00007fff894285b1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
54 com.apple.CoreFoundation 0x00007fff89419c62 __CFRunLoopDoSources0 + 242
55 com.apple.CoreFoundation 0x00007fff894193ef __CFRunLoopRun + 831
56 com.apple.CoreFoundation 0x00007fff89418e75 CFRunLoopRunSpecific + 309
57 com.apple.HIToolbox 0x00007fff858f3a0d RunCurrentEventLoopInMode + 226
58 com.apple.HIToolbox 0x00007fff858f37b7 ReceiveNextEventCommon + 479
59 com.apple.HIToolbox 0x00007fff858f35bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
60 com.apple.AppKit 0x00007fff840f424e _DPSNextEvent + 1434
61 com.apple.AppKit 0x00007fff840f389b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
62 libosxapp.dylib 0x000000012d6d842a -[NSApplicationAWT nextEventMatchingMask:untilDate:inMode:dequeue:] + 124
63 com.apple.AppKit 0x00007fff840e799c -[NSApplication run] + 553
64 libosxapp.dylib 0x000000012d6d823e +[NSApplicationAWT runAWTLoopWithApp:] + 156
65 libawt_lwawt.dylib 0x000000012d66262b -[AWTStarter starter:] + 905
66 com.apple.Foundation 0x00007fff8394f7ce __NSThreadPerformPerform + 229
67 com.apple.CoreFoundation 0x00007fff894285b1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
68 com.apple.CoreFoundation 0x00007fff89419c62 __CFRunLoopDoSources0 + 242
69 com.apple.CoreFoundation 0x00007fff894193ef __CFRunLoopRun + 831
70 com.apple.CoreFoundation 0x00007fff89418e75 CFRunLoopRunSpecific + 309
71 libjli.dylib 0x000000010e55591c CreateExecutionEnvironment + 871
72 libjli.dylib 0x000000010e5516a8 JLI_Launch + 1952
73 net.filebot.FileBot 0x000000010e4d48b0 launch + 7296
74 net.filebot.FileBot 0x000000010e4d2ae4 main + 84
75 net.filebot.FileBot 0x000000010e4d2a84 start + 52




thanks very much for help ;-)
Top
User avatar
rednoah
The Source
Posts: 23931
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:
Contact rednoah

Re: Filebot crashes on launch

Post by rednoah »

Looks like somehow the "Getting Started" page caused a crash. If you start FileBot a second time, does the "Getting Started" still pop up and does it still crash?
:idea: Please read the FAQ and How to Request Help.
Top
lamateur
Posts: 2
Joined: 12 Sep 2015, 12:09

Re: Filebot crashes on launch

Post by lamateur »

Hi,

I started and restarted filebot and the "getting started" page was there each time. I had to click on close button before it crashes and then start filebot again. it seems to be ok now, thanks !

;-)
Top
User avatar
rednoah
The Source
Posts: 23931
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:
Contact rednoah

Re: Filebot crashes on launch

Post by rednoah »

Thanks for reporting! I may not be able to fix the crash, but I can make sure that it will only be shown once even if it crashes.

You can catch up on the Getting Started basics here:
http://www.filebot.net/getting-started/
:idea: Please read the FAQ and How to Request Help.
Top
Post Reply

Return to “Feature Requests and Bug Reports”