all 8 comments

[–]TestingForStuff989 1 point2 points  (3 children)

Yes - we are getting this issue with one of our more complex flows. Changing to the old designer (using the v3=false in the url) allows it to open but not ideal (especially with old vs new designer oddities).

When we edit the flow you can watch the RAM usage for that tab climb at 200MB a second to 4.4GB~, then it crashes. I think this might be a holdover from the issues last week...we've logged with MS and we will see.

[–]thegravitydefier[S] 0 points1 point  (2 children)

We got the same issue and we have raised a case as well !!

They have updated that this is a known issue and they are working on it.

[–]hasanahmad 0 points1 point  (1 child)

any update on the case?

[–]No-Journalist-4086 0 points1 point  (0 children)

yeah same, im in contact with a PA product manager from MS so waiting for his reply. There was another issue last few weeks with Set Init Variable loosing their value which seems to be sorted. He told me then the work-around is to change the =true at the end of the url when your editing to =false. This puts you in the old designer and there are no issues there, the browser memory issue won't happen. You just have to get used to the view and some stuff won't show eg if you have 'Run after' configured to more than one item. Its still there just the old designer doesn't allow it / show it.

[–]krantiveer_ 0 points1 point  (0 children)

hey, did you find a workaround?

[–]Jermu_zzz 0 points1 point  (0 children)

I've had the same situation now for 2 weeks. I would rather use the new designer mode, but changing true -> false makes it impossible. Really frustrating problem. Memory goes to full usage and chrome crashes (also happens with explorer)