I have a problem when resetting device after the state was lost. I can reset the Direct3D device but when i call OnLostDevice function on ID3DXFont i get an error.
First-chance exception at 0x00e6ec05 in Turbo3D.exe: 0xC0000005: Access violation reading location 0xcccccccc.
Unhandled exception at 0x76ee15de in Turbo3D.exe: 0xC0000005: Access violation reading location 0xcccccccc.
When i keep a break point at
Font->OnLostDevice();
I can see that the Font is referring to a memory address 0xcccccccc which is not accessible.
Any Idea how to solve this ?
Related
We are using JavaScriptCore in our iOS application. When deinitializing the module we get this crash
FATAL: Attempting to release access but the mutator does not have access.
Exception: EXC_BREAKPOINT (code=1, subcode=0x1bacbb6fc)
This is the call stack
Any tips on what the reason could be?
I see the following error when getting data from Firebase for my iOS app:
*2018-01-06 14:55:09.327043-0500 Spirit-App[65852:5935746] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'URL must be in the form of http[s]://firebasestorage.googleapis.com/v0/b//o/[?token=signed_url_params]'*
I suspected this may have something to do with Info.plist so as a workaround I attempted to modify the App Transport Security Settings but the same message still appears. Is there another location, besides Info.plist, that would need changed? Or is there a specific location where I can edit the firebase URL referenced above to correct the issue? Thanks!
You are most likely using one of the internal reference functions of Firebase which converts a URL to a storage reference. For e.g. the code below
let httpsReference = storage.reference(forURL: "https://firebasestorage.googleapis.com/b/bucket/o/images%20stars.jpg")
In such an instance, the above exception is thrown if the URL is not in the correct format as explained in the error message. You will need to check that the URL has the valid prefix in the string before passing it to the reference function.
I am trying to answer your question without having a view of your source code where the error is occurring. So if you want more details, please post the source code and I will update my answer.
I have integrated BugSense library available at HERE in my iOS project.
When my application crashed because of uncauchgt exception I can see details in "Errors" bookmark. But when I try to log catched exception (via BUGSENSE_LOG macro), no error details are visible. I want to check my trial version before upgrade.
Could anyone explain me what's wrong? I would appreciate any help
Solved: My problem was because I've tried to log exception which wasn't directly throwed. Somewhere in my code I throw exception (let's suppose A) and in try-catch statement this exception was handled. In catch statement I've created another exception (let's suppose B) by call initWithName: reason: userInfo: and set exception A as caused to B. Log exception B failed, but when I logged A, it works!
I've found that my iOS 5 app is sometimes unexpectedly quited and it does not seem to be due to an uncaught exception, since I've implemented uncaughtExceptionHandler in the app delegate class and I get nothing from there.
If it is because the system is terminating it, it looks like you can only be aware of that if it is in background state: I've read the following line in Apple's documentation.
The applicationWillTerminate: method is not called if your app is currently suspended.
So, if I'm not wrong, you can get the reason why your app is terminated by the system in these cases:
App was in background state
Low-memory event was triggered
Can I detect more causes of why the app is being terminated, in order to report the issue? Or is it possible that it is not currently being terminated, but moved to background without user interaction?
Thanks
NSSetUncaughtExceptionHandler() installs a handler for Objective-C exceptions (e.g. trying to access an NSArray item that does not exist). It does not catch the lower level signals like segmentation fault, bus error, illegal instruction, ..., things that happen when your app for example tries to access an invalid pointer address.
You can also install handlers for those:
#include <signal.h>
void signalHandler(int signal)
{
}
// Somewhere in your start-up code.
signal(SIGSEGV, signalHandler);
My app is coming together now. It's purpose is to search the internet and return JSON data. I realised the importance in catching exceptions such as when there's no internet connection. Now my app will show an alertview explaining that there's no internet connection available - this happens when the NSData returned is nil (because of the lack of internet) so how would I go about catching the exception itself?
You're not looking for an exception, you're just looking for the reachability of the network. This post has great info:
How to check for an active Internet connection on iOS or OSX?