I'm not sure how large "very large" is but it is certainly possible to give the client too much work to cause this type of problem. The createItem call will end up serializing the object which makes a complete copy of it. If you have managed associations, there could be additional work as it has to create the child objects as well.
One way to get an idea of what is going on is to enable the debug logging on the client side: <mx:TraceTarget/>, use the debug player, and look in flashlog.txt in your home directory for the output. That hopefully will make things even slower, but hopefully the trace log will show some evidence of what is taking so long. If that does not show anything, if you can get us a test case I'd be interested to take a look ([EMAIL PROTECTED]). Jeff ________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of box110a Sent: Tuesday, December 05, 2006 1:16 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Flex 2: FDS Freezes Flash player before responders get called I am calling dataService.createItem() a very large Object graph. After I call commit, and my responder is called. the client flash player freezes (browser stops responding, cpu utiliziaiton at 100%) for about 8-10 seconds. I am releasing the itemReference from the createItem() call in the responder. Does anybody have any idea how to debug this problem or figure out what is causing it. thanks, JB
