Uhm, no. Both of those do exactly the same things.
Potential cause 1 : You are making copies of your text or sprite objects. This only performs a shallow copy of the pointer holding the resource, and when they go out of scope they get destroyed. Then when the original goes out of scope, it tries to destroy the same resource a second time, which would crash.
Potential cause 2 : You haven't properly initialized the necessary addons, for the fonts or for the images, which means your load calls will return null, and then when they go out of scope they try to destroy a null pointer, which will crash.
Potential cause 3 : They just aren't loading properly, but you don't check so you wouldn't know.
So, first make sure your resources are loading properly, either through text output, or through exceptions, or whatever else makes you happy.
Second, make sure the addons are initialized.
Third, make sure you don't make copies by value of your text and sprite objects, or write a proper copy constructor.