I took a snapshot of my FF before aborting it. Seems like something is tickling a bug in their security implementation. Phil what URL exactly are you using to fetch your app? I am using http://dueling-banjos.local , not 127.0.0.1, for instance. {Abbreviated trace below]

    1526 Thread_2503
      1526 start
        1526 start
          1526 main
            1526 XRE_main
              1526 nsAppStartup::DestroyExitEvent(PLEvent*)
                1526 nsAppShell::~nsAppShell()
                  1526 RunApplicationEventLoop
                    1526 _AcquireNextEvent
                      1526 ReceiveNextEventCommon
                        1526 RunCurrentEventLoopInMode
                          1526 CFRunLoopRunInMode
                            1526 CFRunLoopRunSpecific
                              1526 PL_ProcessPendingEvents
                                1526 PL_HandleEvent
1526 handleTimerEvent(TimerEventType*)
                                    1526 nsTimerImpl::Fire()
1526 nsPluginInstanceOwner::Paint(nsRect const&, unsigned int) 1526 ns4xPluginInstance::~ns4xPluginInstance()
                                          1526 0x1883f5bc
1526 Flash_EnforceLocalSecurity 1526 Flash_EnforceLocalSecurity
                                                1526 0x186e4823
                                                  1526 0x1854d65b
                                                    1524 0x1854b9c9
                                                      1519 0x1854d37f
                                                        1508 0x18807bd3
1465 0x18807b80 1465 memcopy_mmx 1369 0x18fd21cf 1369 0x18807afe 1325 0x1879180c 1279 0x1878efcc 1275 0x1878ea6e 1036 0x1878d09d 1036 memcopy_mmx 1026 0x18fd238a 1026 memcopy_mmx 1026 memcopy_mmx 1026 memcopy_mmx 1013 0x18111d1b 1013 memcopy_mmx 1013 memcopy_mmx 1007 0x1b11f781 929 0x1b076a1e 851 0x18fd2dc0 851 memcopy_mmx 851 memcopy_mmx 764 memcopy_mmx 421 0x18fd0726 368 0x18fd0bb8 242 0x18807ff3 242 memcopy_mmx

On 2008-07-18, at 09:58EDT, Henry Minsky wrote:

Both Tucker and I are getting the 100% CPU usage and the app doesn't
display.  We tried from
a clean top of trunk.

Is there some other outstanding change you might have in your tree
that isn't checked in?

If I run the app in the fdb debugger, it doesn't print out anything
useful, just seems to load some stuff and then
freeze up before it displays

[SWF] Users:hqm:openlaszlo:trunk:demos:amazon:amazon.lzr=swf9.swf -
159 bytes after decompression
[SWF] Users:hqm:openlaszlo:trunk:demos:amazon:amazon.lzr=swf9.swf -
324 bytes after decompression
[trace] LzSrpite.setColorTransform not yet implemented
[trace] LzSrpite.setColorTransform not yet implemented
[SWF] Users:hqm:openlaszlo:trunk:demos:amazon:amazon.lzr=swf9.swf -
279 bytes after decompression
[SWF] Users:hqm:openlaszlo:trunk:demos:amazon:amazon.lzr=swf9.swf -
401 bytes after decompression
[trace] LzSrpite.setColorTransform not yet implemented
[trace] LzSrpite.setColorTransform not yet implemented
[SWF] Users:hqm:openlaszlo:trunk:demos:amazon:amazon.lzr=swf9.swf -
405 bytes after decompression
[SWF] Users:hqm:openlaszlo:trunk:demos:amazon:amazon.lzr=swf9.swf -
249 bytes after decompression
[SWF] Users:hqm:openlaszlo:trunk:demos:amazon:amazon.lzr=swf9.swf -
219 bytes after decompression
[SWF] Users:hqm:openlaszlo:trunk:demos:amazon:amazon.lzr=swf9.swf -
269 bytes after decompression
[trace] LzSrpite.setColorTransform not yet implemented



On Thu, Jul 17, 2008 at 6:53 PM, Philip Romanik
<[EMAIL PROTECTED]> wrote:
Hi Henry,

I saw that behavior during development, but it stopped when I fixed the loading issues. It tried it in a clean sandbox and I the app loads fine.


Say, when I compile and run amazon in swf9, the app doesn't actually come up, but it sucks down 100% of the CPU in Flash until the browser doesn't
respond.

Does it work for you in a clean tree with your changes?

Maybe I better try a clean tree myself..

On Thu, Jul 17, 2008 at 6:29 PM, Henry Minsky < [EMAIL PROTECTED] >
wrote:
approved!

On Thu, Jul 17, 2008 at 6:10 PM, Philip Romanik
< [EMAIL PROTECTED]> wrote:
Change 20080717-Philip-2 by [EMAIL PROTECTED] on 2008-07-17 17:44:19 EDT
  in /cygdrive/f/laszlo/svn/src/svn/openlaszlo/trunk
  for http://svn.openlaszlo.org/openlaszlo/trunk

Summary: Get amazon app to start in swf9

New Features:

Bugs Fixed:

Technical Reviewer: hqm
QA Reviewer: (pending)
Doc Reviewer: (pending)

Documentation:

Release Notes:

Details:
With these changes the amazon app now starts running. It runs pretty well but there are a number of obvious runtime errors once you start
using it.

LzSprite.as: setSource() is sometimes called with a null argument.
Duplicated behavior of dhtml runtime

amazon.lzx, shoppinglist.lzx:
Changed method start to stopdrag() because of name collision.
Fixed check for array datatype

basecombobox.lzx: second argument to setOpen() is optional

Tests:
Amazon starts and runs to some extent in swf9.
Amazon runs in swf/dhtml. Dragging doesn't always stop when you get
to the borders of the canvas. I'll file a jira task for this.

Files:
M      WEB-INF/lps/lfc/kernel/swf9/LzSprite.as
M      lps/components/base/basecombobox.lzx
M      demos/amazon/shoppinglist.lzx
M      demos/amazon/amazon.lzx

Changeset:
http://svn.openlaszlo.org/openlaszlo/patches/20080717-Philip-2.tar





--
Henry Minsky
Software Architect
[EMAIL PROTECTED]




--
Henry Minsky
Software Architect
[EMAIL PROTECTED]



--
Henry Minsky
Software Architect
[EMAIL PROTECTED]

Reply via email to