Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent

    Extension does not work

    SessionRestore
    3
    7
    126
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      JMO last edited by

      I installed the extension in Safari, but it does not work. I hit the "save" button and it does nothing. I go to the "save current safari session" under the file menu and it does nothing.

      1 Reply Last reply Reply Quote 1
      • SweetP
        SweetP last edited by SweetP

        SessionRestore is only compatible with macOS 10.14.4 and Safari 12.1 or better. make sure your computer and Safari are up to date. the APIs required for SessionRestore were only added in macOS 10.14.4.

        1 Reply Last reply Reply Quote 0
        • Q
          quilter last edited by

          What about Mac OS 10.4.5 which is current ? It autosaves but flashes away when doing manual save. Potential apple fix?

          SweetP 1 Reply Last reply Reply Quote 0
          • SweetP
            SweetP @quilter last edited by

            @quilter it should be working on 10.14.5
            do you see any crash reports related to SessionRestore in this folder:
            ~/Library/Logs/Diagnostic Reports/

            1 Reply Last reply Reply Quote 0
            • Q
              quilter last edited by

              Process: SessionRestore [278]
              Path: /Applications/SessionRestore.app/Contents/MacOS/SessionRestore
              Identifier: SessionRestore
              Version: 1.3.1 (1.3.1)
              Code Type: X86-64 (Native)
              Parent Process: ??? [1]
              Responsible: SessionRestore [278]
              User ID: 501

              Date/Time: 2019-06-08 07:26:59.842 -0500
              OS Version: Mac OS X 10.14.5 (18F132)
              Report Version: 12
              Anonymous UUID: 6163F290-960B-8F06-ED8F-E0047A4934F4

              Time Awake Since Boot: 1100 seconds

              System Integrity Protection: enabled

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

              Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
              Exception Codes: 0x0000000000000001, 0x0000000000000000
              Exception Note: EXC_CORPSE_NOTIFY

              Termination Signal: Illegal instruction: 4
              Termination Reason: Namespace SIGNAL, Code 0x4
              Terminating Process: exc handler [278]

              Application Specific Information:
              Performing @selector(deleteSessions:) from sender NSMenuItem 0x6000008128e0

              Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
              0 com.sweetpproductions.SessionRestore 0x000000010defee78 0x10dee6000 + 102008
              1 com.sweetpproductions.SessionRestore 0x000000010defa96c 0x10dee6000 + 84332
              2 com.sweetpproductions.SessionRestore 0x000000010defab5a 0x10dee6000 + 84826
              3 com.apple.AppKit 0x00007fff301a1844 -[NSApplication(NSResponder) sendAction:to:from:] + 312
              4 com.apple.AppKit 0x00007fff301fda6b -[NSMenuItem _corePerformAction] + 323
              5 com.apple.AppKit 0x00007fff301fd7dc -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 114
              6 com.apple.AppKit 0x00007fff301fc64e -[NSMenu performKeyEquivalent:] + 363
              7 com.apple.AppKit 0x00007fff30681d9f routeKeyEquivalent + 860
              8 com.apple.AppKit 0x00007fff2feba32c -[NSApplication(NSEvent) sendEvent:] + 1064
              9 com.apple.AppKit 0x00007fff2fea8874 -[NSApplication run] + 755
              10 com.apple.AppKit 0x00007fff2fe97d7c NSApplicationMain + 777
              11 com.sweetpproductions.SessionRestore 0x000000010dee7f39 0x10dee6000 + 7993
              12 libdyld.dylib 0x00007fff5e7543d5 start + 1

              Thread 1:: com.apple.NSEventThread
              0 libsystem_kernel.dylib 0x00007fff5e88922a mach_msg_trap + 10
              1 libsystem_kernel.dylib 0x00007fff5e88976c mach_msg + 60
              2 com.apple.CoreFoundation 0x00007fff3282abee __CFRunLoopServiceMachPort + 328
              3 com.apple.CoreFoundation 0x00007fff3282a15c __CFRunLoopRun + 1612
              4 com.apple.CoreFoundation 0x00007fff328298be CFRunLoopRunSpecific + 455
              5 com.apple.AppKit 0x00007fff2feb76a6 _NSEventThread + 175
              6 libsystem_pthread.dylib 0x00007fff5e9482eb _pthread_body + 126
              7 libsystem_pthread.dylib 0x00007fff5e94b249 _pthread_start + 66
              8 libsystem_pthread.dylib 0x00007fff5e94740d thread_start + 13

              Thread 2:
              0 libsystem_pthread.dylib 0x00007fff5e9473f0 start_wqthread + 0

              Thread 3:
              0 libsystem_pthread.dylib 0x00007fff5e9473f0 start_wqthread + 0

              Thread 4:
              0 libsystem_pthread.dylib 0x00007fff5e9473f0 start_wqthread + 0

              Thread 5:
              0 libsystem_pthread.dylib 0x00007fff5e9473f0 start_wqthread + 0

              Thread 0 crashed with X86 Thread State (64-bit):
              rax: 0x00007fff94ffa6e0 rbx: 0x00006000013183c0 rcx: 0x00fffffffffffff8 rdx: 0x00000000ed40204a
              rdi: 0x00000000ed20182f rsi: 0x000060000070dff0 rbp: 0x00007ffee1d192f0 rsp: 0x00007ffee1d191c0
              r8: 0x0000000000000091 r9: 0x00000000000007fb r10: 0x0000000000001ff0 r11: 0x0000000000000070
              r12: 0x00007fff8da74430 r13: 0x00006000017185b0 r14: 0x0000000000000001 r15: 0x00007fff94ffa6e0
              rip: 0x000000010defee78 rfl: 0x0000000000010246 cr2: 0x00007fc89393a000

              Logical CPU: 0
              Error Code: 0x00000000
              Trap Number: 6

              1 Reply Last reply Reply Quote 0
              • SweetP
                SweetP last edited by

                I am aware of this crash, but haven't been able to reproduce it. this is related to deleting sessions, and is not all that common as far as I know

                1 Reply Last reply Reply Quote 0
                • SweetP
                  SweetP last edited by

                  this crash was fixed in v1.3.2
                  🙂

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post