Crash upon launch (OS X 10.7) #397
Labels
Comments
|
The latest GitX also crashed upon launch on Yosemite. |
|
I have GitX 0.15.1899 (latest is 1962) running well on Yosamite. If that helps in any way. On 5 בנוב 2014, at 18:42, Didip Kerabat [email protected] wrote:
Motti Shneor mobile: +972-54-3136621Ceterum censeo Microsoftinem delendam esse |
ghost
mentioned this issue
|
@Motti-Shneor sorry to hear that you're having trouble. Are you running the application from your The last build to support OS X 10.7 was 0.15.1949. Unfortunately I just don't have the time and resources to develop against older OS releases - it's nearly too difficult as is to keep my Macs running clean environments of the next-to-latest, latest, or beta versions of OS X for professional use. The in-app update should not have offered the incompatible build to you, did it update you to the broken version from the automatic update system, or did you download it yourself? @didip, the Yosamite crash should be fixed in the latest build. |
|
I am also experiencing this crash upon launch. Here is the full log: |
|
Hi, and thanks for the fast reply.
Now I'm stuck... Could you point me to a tag or commit in the code-base I could use to checkout and re-build 0.15.1949 for myself? I really need it. I still program on my 10.7.5 iMac (which cannot be upgraded to anything newer), and have many repositories on that computer. Thanks again. On 10 בנוב 2014, at 16:03, Rowan James [email protected] wrote:
Motti Shneor mobile: +972-54-3136621Ceterum censeo Microsoftinem delendam esse |
|
@Motti-Shneor 0.15.1949 is avalable here: Or from the GitHub releases page: I'll investigate why you were offered the update, that should not have happened. |
|
@RohitRox That crash should be fixed in the latest build, available via in-app update or directly here: |
ghost
mentioned this issue
|
(sorry about the barrage of rewrites, can't figure out how to delete the wrong commits) |
|
If anyone trusts me and wants to test this fix I uploaded a build here http://cl.ly/YVDz/download/GitX-dev-1964b.dmg That includes my last three pull requets #405, #400, and #399. |
|
@micampe also, this issue is for a 10.7 bug, please don't side-track it. |
|
Sorry, I didn't realize this was only for 10.7, I get the same crash on 10.10. The responder chain fix avoids the crash but causes the windows to not be restored correctly, as described in #402. Using the old SDK was meant as a temporary workaround, I suspect these issues are due to changes in behavior in |
|
Ah, do you get the reported crash, or the forwardMethod loop that RohitRox pasted into this issue? |
|
The forwardMethod loop. |
|
Cool; sorry. That one got pasted into a whole bunch of issues before I could get the workaround out. I expect the SDK change would have less side-effects in the build, but it requires developers to have the older SDK (which I don't currently, having just done a clean install on my main workstation to get 10.10 to reproduce and "fix" the |
|
I beg to differ. Moving immediately to a new base SDK without scanning changes and per-adapting all your code base to the changes, is the more irresponsible move. Apple promises compatibility for older applications, not for new SDK's. If you maintain a program used by many people, you update the SDK and do your code updating on a side branch. Never on the branch from which you release the software. The big changes in the responder chain (NSViewController auto insertion) is but one of the many changes. I am pretty sure GitX isn't ready for all of them. Doing your testing on the users back isn't nice. People actually rely n the software for daily work. I'd like to help in development if you need any help. I really like GitX Motti נשלח מה-iPad שלי ב-14 בנוב 2014, בשעה 03:19, Rowan James [email protected] כתב/ה:
|
|
I agree with @Motti-Shneor. Adopting new SDKs should be an explicit action, not a side effect of updating your OS (which is what happens when you use the Latest OS X Base SDK setting), because it will itself cause other unexpected side effects. But we are still discussing this in the wrong issue. This conversation should probably move to #405. |
|
GitX-dev-1964.dmg fixed the issue for me. Thnks rowanj |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
not much to say. GitX 0.15.1962 crashes immediately at launch on my old iMac 6,1 running Mac OS X - 10.7.5 (Latest Lion).
My mac can't run anything later than 10.7.5. It has 32bit kernel, but runs 64bit apps no problem.
GitX crashes, and only then I get the OS-X dialog asking me to allow it to run, since it was "from the internet." So if the system hasn't yet launched it, how did it crash??? a bit weird.
Maybe your info.plist is broken? some initial thing that crashes as the launchd looks into the app bundle?
If there's anything I can do to help fix the problem --- just ask. Here's a copy of the rather short crash report: (No stack, no threads, this is really at the beginning).
Process: launchd [14132]
Path: /Volumes/VOLUME/GitX.app/Contents/MacOS/GitX
Identifier: net.phere.GitX
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: launchd [277]
Date/Time: 2014-11-04 21:29:26.686 +0200
OS Version: Mac OS X 10.7.5 (11G63)
Report Version: 9
Interval Since Last Report: 338446 sec
Crashes Since Last Report: 6
Per-App Crashes Since Last Report: 5
Anonymous UUID: 131E3037-870B-4345-91A4-310C706E6DDD
Crashed Thread: Unknown
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007fff5fc01028
Backtrace not available
Unknown thread crashed with X86 Thread State (64-bit):
rax: 0x0000000000000055 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x0000000000000000
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x00007fff5fc01028 rfl: 0x0000000000010203 cr2: 0x00007fff5fc01028
Logical CPU: 0
Binary images description not available
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 2
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 54046
thread_create: 0
thread_set_state: 0
Model: iMac6,1, BootROM IM61.0093.B07, 2 processors, Intel Core 2 Duo, 2.16 GHz, 4 GB, SMC 1.10f3
Graphics: NVIDIA GeForce 7300 GT, NVIDIA GeForce 7300 GT, PCIe, 128 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F98000000000000, 0x393930353239352D3034352E4130314C4600
Memory Module: BANK 1/DIMM1, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F98000000000000, 0x393930353239352D3034352E4130314C4600
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x87), Broadcom BCM43xx 1.0 (5.10.131.36.15)
Bluetooth: Version 4.0.8f17, 2 service, 18 devices, 1 incoming serial ports
Network Service: Built-in Ethernet, Ethernet, en0
Network Service: AirPort, AirPort, en1
Serial ATA Device: Hitachi HDS723020BLA642, 2 TB
Parallel ATA Device: MATSHITADVD-R UJ-85J
USB Device: Built-in iSight, apple_vendor_id, 0x8501, 0xfd400000 / 6
USB Device: Photosmart C7200 series, 0x03f0 (Hewlett Packard), 0x6511, 0xfd500000 / 4
USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0xfd100000 / 2
USB Device: Apple Optical USB Mouse, apple_vendor_id, 0x0304, 0xfd130000 / 5
USB Device: Apple Keyboard, apple_vendor_id, 0x0221, 0xfd120000 / 3
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8206, 0x7d100000 / 2
USB Device: IR Receiver, apple_vendor_id, 0x8240, 0x7d200000 / 3
FireWire Device: unknown_device, unknown_speed
The text was updated successfully, but these errors were encountered: