Authorware 7 - Memory Error
in [Authorware]
|
Prev: Replacement software for Authorware
Next: Quiz
From: sc_honeydo on 9 Jan 2008 09:59 I am currently using Authorware 7. Just the basic functionality....no custom functions, no videos, nothing out of the ordinary. Just basic read this, click continue....maybe a little movement of some pics, but that is it. Some days (most days) I go to start Authorware, and when I select to open my file (or any file for that matter) I get "The instruction at "0xs0057e5fb" referenced memory at "<address here...it changes>". The memory could not be "read". Click OK to terminate the program. Click on CANCEL to debug the program." This morning after 14 tries, I could open my file. THEN, sometimes, never knowing when, it'll crash with this same error when trying to run, save, click on something, do anything. Doesn't really matter what you are doing, it's flippy. Any thoughts on how to get this error to go away? Yes, we already replaced the memory in the machine, conincidently b/c I just needed more given I was using lots of programs. But Now, I have everything else closed in order to let AW use all of it to its heart's content. Any thoughts are greatly appreciated. Thanks.
From: Erik **AdobeCommunityExpert** on 9 Jan 2008 12:11 The biggest cause of crashes with A'ware 7, IME, is the Property (Inspector) Panel. It seems to forget it's showing already and another instance of it opens on top of the existing one, then another, then another... I've had Authorware projects open and undocked the panel, just to see another below it, and another below that, etc. Now I ALWAYS leave the panel undocked and close it whenever I can. SO, open Authorware and if the Property Panel is open, close it, and close any other instances below it. Then open your project, and you may see that panel open again, and flash a few times as other instances are opened again and again. Close them all, if you can, before the application crashes. Save your project. Exit Authorware. Hopefully the next time you open Authorware and/or that project, the panel(s) won't appear automatically. Erik sc_honeydo wrote: > I am currently using Authorware 7. Just the basic functionality....no custom > functions, no videos, nothing out of the ordinary. Just basic read this, click > continue....maybe a little movement of some pics, but that is it. > > Some days (most days) I go to start Authorware, and when I select to open my > file (or any file for that matter) I get > "The instruction at "0xs0057e5fb" referenced memory at "<address here...it > changes>". The memory could not be "read". Click OK to terminate the program. > Click on CANCEL to debug the program." > > This morning after 14 tries, I could open my file. THEN, sometimes, never > knowing when, it'll crash with this same error when trying to run, save, click > on something, do anything. Doesn't really matter what you are doing, it's > flippy. Any thoughts on how to get this error to go away? > > Yes, we already replaced the memory in the machine, conincidently b/c I just > needed more given I was using lots of programs. But Now, I have everything > else closed in order to let AW use all of it to its heart's content. > > Any thoughts are greatly appreciated. > > Thanks. > -- Erik Lord http://www.capemedia.net Adobe Community Expert - Authorware http://www.adobe.com/communities/experts/ ------------------------------------------------------------------------ http://www.awaretips.net - samples, tips, products, faqs, and links! *Search the A'ware newsgroup archives* http://groups.google.com/group/macromedia.authorware
From: Steve Howard on 9 Jan 2008 12:13 I thought the multiple property inspectors only happened if you are using JumpFile/JumpFileReturn? I never have my property inspector docked, so I've not encountered any of that other stuff you described. To be honest I thought all of that had been fixed with the 7.02 update. Steve
From: Erik **AdobeCommunityExpert** on 9 Jan 2008 12:29 I don't know if that errant behavior is restricted to just when JF/JFR are used, but those functions sure increase the chances of the problem. The poster doesn't state whether her last project used those functions, so threw it out there since it's the only thing that's made my Authorware apps crash in the recent past. The 7.02 update definitely did not address the issue as I assuredly run 7.02 on my installs and found this issue less than a year ago. My panel is never docked now either. The multiple-instance builds can occur whether it is or not. Erik Steve Howard wrote: > I thought the multiple property inspectors only happened if you are > using JumpFile/JumpFileReturn? > > I never have my property inspector docked, so I've not encountered any > of that other stuff you described. To be honest I thought all of that > had been fixed with the 7.02 update. > > Steve -- Erik Lord http://www.capemedia.net Adobe Community Expert - Authorware http://www.adobe.com/communities/experts/ ------------------------------------------------------------------------ http://www.awaretips.net - samples, tips, products, faqs, and links! *Search the A'ware newsgroup archives* http://groups.google.com/group/macromedia.authorware
From: PFTW on 9 Jan 2008 13:08
I'm getting the exact same error. What the original posteer probably failed to mention is that he's probably running a web-packaged piece. If he isn't, then I'm sorry to invade on your post, but I also need help with this issue. Some background: I have a bunch of online courses built with AW 6.5 and running on the 6.5 webplayer that have been running fine for the past 4 years. The firm I'm working for has been running Windows 2000 on their desktops. Now they're upgrading to Windows XP firm-wide (Thousands of desktops). While testing the online courses the memory error comes up seemingly arbitrarily. Are there any known memory issues with AW 6.5 webplayer running on XP? I haven't upgraded to V 7 yet because it would require the retesting of the webplayer (the rules on what gets installed on the desktops here are very strict about that here) and the repackaging of all the online courses and that would take months. |