Comment 1 for bug 1167147

I am not sure why this happened, But I noticed this problem in my unparsed-text branch, It seems it seems the error was being run but catched by another part of the code therefore ignores, I am not actually when or where this error happens since I tried to debug it with no look. Even though I fixed the error throw by checking for this error before asking for the resource that holds the text and this solved the problem.

I will link this bug to my other branch with holds the fix.