[Animated] getting "Object.isFrozen can only be called on Objects" intermittently

[lelandrichardson]

I haven't been able to get a base-case repro, but I seem to be getting the following error every once in a while when working with the animated API.

Anyone know what this might be an indication of?

[ide]

Probably easiest to set a breakpoint in the debugger on all exceptions and inspect what the bad value is (could be something like null or false).

[lelandrichardson]

@ide I'm trying but i'm experiencing another issue where I can't seem to debug in chrome :/ argh.

[ide]

You can use the Safari debugger by going to Develop > iOS Simulator > JSContext. It's not as good but should help a lot letting you set breakpoints and inspect the stack.

[brentvatne]

@lelandrichardson - is this happening with the Formula API that you're working on? or the base API? Also, is this occurring against master? precomputeStyle was updated recently to add some additional rotation/perspective properties, that may have had an effect.

[lelandrichardson]

@brentvatne it's happened a couple of times, some of which were before I was using a fork. I'll make sure I'm working with the latest version of master, though. It hasn't happened in a while which is why I haven't updated this with more information, but I'm also on vacation so only working a couple hours/day.

Next time this happens with the debugger open I'll definitely try and figure out what path it's going through, but it's not happening to me very often any more.

[brentvatne]

Awesome, enjoy the vacations @lelandrichardson 😄 🚀

[brentvatne]

@vjeux - any idea what is going on here? based on deepFreezeAndThrowOnMutationInDev Object.isFrozen should never be called on a non-Object; it should escape early when the typeof check fails. cc @spicyj

[lelandrichardson]

@brentvatne I have had it happen several times since I opened this ticket, but I can't seem to get it to happen while I have the debugger running to see why it's happening...

Edit: I am still working off of 0.8.0-rc2 though.... I'll upgrade and let you know if I see it again.

[ide]

Maybe in your fork wrap that piece of code in try-catch and print out the bad value when it happens?

[sophiebits]

Maybe some sort of host object. I could imagine if you tried to freeze a DOM node, for example, then it could give that error – but I'm not sure how many such objects we have in the RN environment. Not many.

[lelandrichardson]

@ide i'll give that a shot

[corymsmith]

Any updates on this? I'm running into the same issue with the Spinner component I just added to React Native Icons

[nikoladimitroff]

@ide, @lelandrichardson What's the state of this issue? I encountered the same problem on Android and this JSX reproduces the crash 100% of the time, though sometimes it crashes after 30 seconds and other times almost instantly after startup. The app is a simple fluid grid with many cells, each containing a box. On startup, all the cells start moving from left to right and back again. (I do know that I can translate the entire container, this was created as a performance test, not a usability one).

The app works on iOS but has terrible performance - only 100 cells get the frame rate down to about 25 fps in release builds on a 5th generation iPod (iOS 8.4). Am I misusing the animation API or is this a worst-case scenario?

[ide]

@nikoladimitroff I've never encountered this issue -- it'd help a lot if you could add breakpoints / console.log statements to identify what the cause is.

You could try putting overflow:hidden on each cell and removeClippedSubviews on the ListView, though I have seen that the UIExplorer's animation example runs poorly on an iPod touch.