fxAbort Memory Issues with new update

Watchface discussion
1

Hey guys, I’ve been developing a fun Yoshi Flower watch face on the discord, but after the last update nothing will launch. On the CloudPebble emulator it ran fine two days ago, but now it just hangs on this screen and gives me:

[PHONE] pebble-app.js:?: pebble-js-app.js:151 @moddable/proxy launched
[ERROR] xsPlatform.c:125: fxAbort memory full:

(I do not currently have my PR2 yet, so I am restricted to testing on CloudPebble Emulation)

If I need to scale back the scope of the face I can do that, just want to know how much memory I have compared to last build. Been learning a lot about shrinking PDCs to 1KB or less!

image
image206×272 2.25 KB

How it ran before, for reference: About 12 animating PDCs that animate on watch tap, then become static after 5s.

It ran on both Emery & Gabbro (at least the emulator, I dont have my PR2 yet)

2

I’m having the same issue with a (moderately complicated) private Alloy-based watchface I’m working on.

I haven’t had time to investigate so I can’t offer any help at the moment … but this was on real PT2 hardware and, for now, I’ve reverted the watch to the previous firmware.

I’m glad to see it’s not just me! I hope somebody from Core/Pebble can look into it!

1 Like
3

A watch face I like won’t open (and crashes the watch, PT2, when I try) following the recent update.