Illegal call to StaticFindObject() while serializing object data!

Development Platform & Builds
, , , ,
1

Hello,

we just ported our project to 4.12 and when trying to play in Standalone or packaging we get the following error:

93165-illegalcalltostaticfindobject.png
93165-illegalcalltostaticfindobject.png710×447 105 KB

We found this thread, with an error sounding similar:
[https://answers.unrealengine.com/questions/405539/garbage-collector-error-with-blueprint-hierarchies.html][2]

Please help us, we cannot continue with our development because of this.

Cheers

UPDATE: we narrowed down the issue. It happens during the auto-saving of our levels at the beginning of the packaging process. By pressing ‘Cancel’ during the saving of the two final levels, we can continue to package without the crash.
Saving the levels by hand works perfectly fine. Quite strange, but at least we can build again…

It’s just a workaround though and should be addressed asap nontheless…

2

Hi Priareos,

  • Does this occur in a clean, blank project with no additional content or is it limited to one project?
  • What engine version were you using before you moved to 4.12 with the project?
  • What steps can I take to reproduce this error on my end?
3

Hi Priareos,

We have not heard from you in several days. I am marking this as answered for tracking purposes. If you are still experiencing this error, please comment with the requested information.

4

Hi ,

We compiled the engine from the 4.12.0 github release branch (we also tried 4.12.1) in order to support XboxOne development. Before that we were using the 4.11.2. I am pretty sure it does not happen in a clean project, and i cannot really tell you how to reproduce the issue.

Within our project we use one persistent level with several sub-levels. By launching in standalon (or packaging), all levels are saved automatically and that’s when the error occurs.

Our workaround (canceling the save for the last two of these sub-levels) lets us package, however, we cannot launch the game in standalone anymore. I could send you our project via pm, if you like.

5

If you remove the contents from the contents folder do you see the same error? If not, try slowly adding content back to the contents folder until the error occurs again. Typically it is best to start with either C++ or blueprint classes, as these are the most likely to cause errors such as this. Additionally, try running “Fix up Redirectors” on the contents folder with everything in it.

6

fixed for us in 4.12.3. might be the engine update did it or we changed things internally…

7

I’m happy to hear this is no longer occurring for you. I am remarking this as answered for tracking purposes.