Closed lukasberns closed 12 years ago
All of the crashes that have been made available to me through Apple's diagnostics program are fixed in the repo currently.
It'd be nice if you, as you say, could send me a crash report of the crash you're seeing. Then I can tell you whether it's fixed or still present. :-)
Lukas,
Have you been able to get any crash reports for this?
Mikkel
Sorry Mikkel for the late reply
I wanted to upload the crash reports, but I got into the unexpected trouble that everyone had already installed iOS 5.1, whose SDK is not available for Snow Leopard (I have a 32 bit MacBook and can't install Lion). So I couldn't get the crash logs. Bummer
I have some old logs, which might be of a pre-release version. How shall I send them to you? Are crash logs safe to be posted in public?
The exception info
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x400015fc
Crashed Thread: 7
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x90000008
Crashed Thread: 7
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x70000008
Crashed Thread: 7
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x30000008
Crashed Thread: 7
Looks like it's the same error 4 times? (top two and bottom two each on same device)
Not sure I follow. If you've gotten crashes with the 1.0 version on the App Store, your crash logs should be synced to your machine via iTunes. If this is with your own build, I can't really use them without the correct .dSYMs. :(
Anyway, crash logs from iTunes are in ~/Library/Logs/CrashReporter/MobileDevice/
There shouldn't be any personally identifying or anything that makes the crash reports bad to show publicly, but I'd prefer email if possible. (mkrautz@mumbleapp.com)
Lukas, have you been able to reproduce this in the 1.1 release? Thanks.
I haven't been able to test it much yet, but I haven't had any crashes so far :)
Ok I spent a little time doing a few tests now. With 1.0 I could easily crash the app by causing constructive resonance, but I with 1.1 the app survived my "attacks" for more than 20 minutes. Looks very solid! I will close this issue. Thanks!
When mumble receives a loud sound, the app (app store version 1.0) crashes sometimes. You can test e.g. by causing feedback (hold mumble-iPhone close to a PC running mumble). I'm not absolutely sure if the loud sound is the cause, but I observed crashes on about 5 different devices.
I will send some crash logs later. Love the app.