Editor freeze since new Stable build

Anyone else getting an Animation Editor freeze once you try to close the editor?

I'm using a project folder. I have quite a few animations - although I haven't added any since the new update. I would import some sprite sheets and about 3 times in one day I just got a spinning cursor and Construct would freeze.

It's only super noticeable because that NEVER happens and only started today when I started using the new stable build r336.

I thought maybe it was the performance setting in Chrome that I turned on a few days ago, but no its not that.

I just loaded up my project, replaced about 4-5 animations by importing sprite sheets and it just hung.

something is definitely wrong!

here is the console, no idea if this helps!

and...

I don't really know how to reproduce it. So I was just wondering if others were getting it.

Ribis

That looks like an error coming from an extension, the extension is probably ignoring it, but C3 catches it. There have been reports of the Last Pass extension causing it, but it could be any number of extensions. Try disabling your extensions one at a time to try and figure out which one is the problem or just turn all extensions off when using C3.

jobel

What kind of images are you using? As in size, amount of frames and format.

DiegoM On one Sprite object I have about 150 animations. All are 8 frames that loop and are 64x64 in size (pngs).

They also share the same collision boxes so I am often importing a sheet and then right-clicking Apply to all animations.

I've noticed if I do a number of these re-imports without saving is when it happens. If I do one at a time, close and save, it seems to avoid the issue.

I also am using a Project Folder Save. So it feels like save thing maybe?

It happened to me several times too. The editor was completely frozen and I had to close c3 without saving.

I'm using project folder.

I just got the freeze after importing multiple frames into a sprite (across multiple animations).

Then I restarted C3 and repeated the process, and it froze again!

So I tried doing it again and now it's all good, no longer freezes! So I tried multiple times more, and I'm unable to duplicate this issue, very strange.

Unrelated to the issue with Animation Editor, but the GSI error that Jobel shows comes from GoogleSignIn, it seems you (the editor or your servers) have some issue with credentials or loading of data which you also need to look into DiegoM.

Also all the "inline" errors with the CSS should be fixed, very irritating when the console is full of errors/warnings just with a regular loading.

You can see the error messages above from Jobel, I get the same.

alastair

To me, it feels like it only happens when I've imported lots frames and had the animation editor opened for a long time, maybe doing other things like deleting frames or using hotspot.

So my workaround is to just import the frames, then quickly close the animation editor, then save, then open it again and continue work in the anim editor with placing hotspots and such.

YES this exactly. I know bugs you can't reproduce are SUPER annoying. But I feel like this is good place to start for the Construct team to reverse engineer because its so hard to reproduce.

I forgot to mention it but this is happening to me since at least r332 (not just since last stable r336 release)

Overboy were those betas? I only use Stable versions and this issue was so blatantly obvious since I have been doing the same things this whole past month and as soon as the Stable version dropped I got the freeze.