Runtime Crash & Flash v.10

[runtime crash]

To those of you experiencing the runtime crash when editing large photos: we've got some great news! Adobe just released the newest version of Flash10: 10.0.22.87, which appears to be significantly more stable.

If you are experiencing runtime errors, please upgrade to the newest version of Flash10 using these 2 steps:

 1. Uninstall your current flash player first: Uninstall here!
*Make sure you not only download, but also open and run the uninstaller!

 2. Then install the newest Flash player (10.0.22.87): Install here!

A little bit of context:
Picnik runs in an Adobe product called Flash.  Flash 10,0,12,36 has a nasty bug where if you hit +1gb after some heavy editing on a big photo, Flash (and usually your browser) crashes. To find out which version you are running  check here.

We've been trying to keep Picnik effects from hitting that high memory mark. We collected info on which tools and effects pushed Flash over the 1gb threshold and adjusted them to use less temporary memory space.

We recommended then, and still recommend now, resizing your photo down to keep you under this memory level.  Try resizing (Edit:Resize) into the 1024px range assuming you're not going to Print the photo.  If printing, is good to keep it in the bigger 2000px range. This helps Picnik run quicker and smoother.

If you're running 10.0.22.87 and you have any comments, questions, updates, or issues to report, please post here!

We hope this gets many of you on the right track!
-Ali, Team Picnik

UPDATE: it looks like there are still runtime crashes occurring with Flash 10.0.22.87. It will still be helpful to upgrade, but it looks like it's not the cure-all we'd hoped for. Please keep us updated on any troubles or joys you experience with 10.0.22.87 in this post!

I have the current Flash player as listed and I'm encountering Runtime errors.

Just wanted to let you know since your post was from Feb,2009.

Hello cysco12 and others-

Thank you for the update.

It's true, we continue to have trouble with the runtime monster. While we're still waiting for Adobe to release a version of the flash player that will not crash when your temporary memory usage hits 1GB, we also bear the responsibility of keeping our effects and other processes from using too much memory.

We're working on a creative way to allow users to still work with their large resolution files while not causing high memory usage. We don't have any intentions to lower the maximum resolution limit, but until this issue is resolved, it means that users will every now and then hit the runtime issue unless they chose to manually resize their image smaller.

This issue is a priority for us and we couldn't be more thankful for how patient you all have been. We appreciate your continued concern and we are addressing the runtime situation as best we can. We've got a few solutions on the horizon and they'll be coming as fast as we can put them together.

I hope this helps to clarify for you.

Thank you,
Ali, Team Picnik

I am still experiencing this problem Ali.  I have been trying to edit a photo for two days after resizing and am still experiencing a crash issue.  It is really frustrating to pay for premium, yet not be able to use most of the premium services now because they cause Picnik and the browser to crash. 

Note to all:
Christinaz and I have been discussing this issue through Flickr.

We discussed the path she's taking in Picnik that prompts this error and it looks like her expert use of a large variety of effects and tools is overloading her temporary memory space and unfortunately prompting the runtime error.

The suggestions I had for her while we're working on keeping the memory use down for these processes is to keep her picture a little smaller, try a few different browsers, and, for the time being, save intermittently to avoid losing a long series of work.

If you too are using a lot of Picniky goodness before hitting the error, consider saving your image and then hitting the refresh button before continuing your work, this way you will not lose any of your edits (they'll all be waiting for you in your History folder) and you'll reset the memory usage since flash seems to be having some trouble recovering the memory it's no longer using after a process is over. A pain, for sure, but better than losing your image.

At the moment, if you chose not to resize your image smaller, or save between every few edits, you'll have to risk the runtime monster. We have prioritized this and hope to have some creative solutions out for you as soon as we can.

Thank you christinaz, and thank you all, for your patience.
-Ali, Team Picnik

Just wondering if there is any further info on this. As I am still having this issue quite often. However it's not so frequent with firefox than it is with IE. I am using the lastest flash version, but I do keep my images at full size as I print. I do use a lot of features on each image and find it happens most often when cloning so I am saving frequently and then choosing to continue editing.

Is there a further solution or do I just have to accept that the amount of work I do on my images is more than picnik is able to handle.

Hey Trigbagger,

Thanks for checking back with us. As it stands it sounds like you are doing all the right things. No new developments have come of this yet, however we have found that using Google Chrome as your browser when editing with Picnik is the most reliable. If you aren't wanting to downsize your images this may be the only other solution for you at this time.

Cheers,

Chelsea - Team Picnik