We can find out for you: just after you encounter the error, Squeak writes

a file named SqueakDebug.log into its current directory. Feel free to post

the contents of the file here and I'll see that I find you the bug.

Is there a profiler in Squeak I can search for the problem myself with?

MessageTally spyOn: code you want to trace

Will show you where the problem lies.