Alex, THANKS IN ADVANCE for asking around on this. Please keep me posted, as I'm trying to figure out why we're seeing such odd behavior from FlexPrintJob.
Best Steve --- In flexcoders@yahoogroups.com, Alex Harui <[EMAIL PROTECTED]> wrote: > > I have no idea why you see that output. I'll ask internally > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of steve_kellogg_davita > Sent: Friday, September 05, 2008 11:08 AM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] Re: Memory Thrashing during PRINT operations. > > > THANKS for your response. > > Our swf is called main.swf.. > > There aren't any modules in my app (yet), so it's just one big SWF. > > I SUSPECT that it's loading, and unloading resources in the SWF > (images, or something?) as needed to keep the movie running. Just to > be clear, there aren't ANY images in the document pages that I'm > trying to print. > > Does that make ANY sense from a Flash runtime perspective? > > Steve > > --- In flexcoders@yahoogroups.com<mailto:flexcoders%40yahoogroups.com>, Alex Harui <aharui@> wrote: > > > > Is you swf main.swf or could it be loading some sort of small main.swf? > > > > From: flexcoders@yahoogroups.com<mailto:flexcoders%40yahoogroups.com> [mailto:flexcoders@yahoogroups.com<mailto:flexcoders%40yahoogroups.com>] > On Behalf Of steve_kellogg_davita > > Sent: Friday, September 05, 2008 8:37 AM > > To: flexcoders@yahoogroups.com<mailto:flexcoders%40yahoogroups.com> > > Subject: [flexcoders] Memory Thrashing during PRINT operations. > > > > > > Hello, > > > > I'm running into some trouble that I hope you guys can offer some > > insight on. > > > > When using FlexPrintJob to print a document with multiple pages > > (typically, anything more than 2 or so), I'm seeing a bunch of trace > > messages that APPEAR to suggest that objects in memory are being > > loaded/unloaded, or that memory is otherwise getting thrashed around... > > > > FOR EXAMPLE.. > > > > The following code.. ("page" is a UIComponent) > > > > trace("+"); > > myPrintJob.addObject(page, FlexPrintJobScaleType.MATCH_WIDTH) ; > > trace("-"); > > > > is producing the following result.. > > > > + > > [SWF] /htdocs/main.swf - 1,805 bytes after decompression > > [SWF] /htdocs/main.swf - 2,441 bytes after decompression > > [SWF] /htdocs/main.swf - 2,346 bytes after decompression > > [SWF] /htdocs/main.swf - 2,389 bytes after decompression > > [SWF] /htdocs/main.swf - 2,156 bytes after decompression > > [SWF] /htdocs/main.swf - 1,861 bytes after decompression > > - > > > > As you can see, I'm putting the "+/-" traces in to confirm that these > > other messages are being output DURING the addObject call. > > > > For EVERY page I add (after the first two), I see this EXACT sequence > > of [SWF] messages (including the exact bytecounts). > > > > In addition to just being annoying, this sequence takes 2-3 seconds > > per page, which obviously limits the total number of pages I can print > > before the 15 second timeout occurs.. > > > > SO, here's the question... Does anyone have any insights into this? > > Are there any settings that I can use to alert the machine running my > > app that it needs to allocate more memory to the SWF's version of a > heap? > > > > When I originally wrote the print wrapper dialog for this application > > (in Flex 2), I don't remember seeing any of this, and it was tested > > with HUNDREDS of pages per printJob, so I SUSPECT that this is a new > > behavior in Flex 3. > > > > Thanks in Advance for any assistance. > > > > Steve > > >
