Dreamweaver CS4 attempted to free unallocated memory bug

Dreamweaver CS4 Mac version 10.0.0.4117 has a fatal bug. It is trying to free up unallocated memory. Most likely, it is trying to free the pointer twice, which ended up attempting to free memory that does not belong to it. This corrupts the system memory, and bring down Snow Leopard, causing the notorious freeze problem in Snow Leopard.
See the system log, right after Dreamweaver crashed, it corrupted the system memory, causing Safari to freeze right after that:
Mar 30 14:08:32 Dreamweaver[505]: Dreamweaver(505,0xa0aae4e0) malloc: *** error for object 0x2fac3a90: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Mar 30 14:08:32 [0x0-0x32032].com.adobe.dreamweaver-10.0[505]: Dreamweaver(505,0xa0aae4e0) malloc: *** error for object 0x2fac3a90: pointer being freed was not allocated
Mar 30 14:08:32 [0x0-0x32032].com.adobe.dreamweaver-10.0[505]: *** set a breakpoint in malloc_error_break to debug
Mar 30 14:10:23 Safari[216]: Periodic CFURLCache Insert stats (iters: 1107) - Tx time:0.285461, # of Inserts: 16, # of bytes written: 276255, Did shrink: NO, Size of cache-file: 181460992, Num of Failures: 0
Here is the log that shows the repeated error:
Mar 30 15:28:33 [0x0-0x47047].com.adobe.dreamweaver-10.0[887]: objc[887]: Class ApolloPasteboardSource is implemented in both /Applications/Adobe Dreamweaver CS4/Configuration/Flash Player/AuthPlayLib.bundle/Contents/MacOS/AuthPlayLib and /Applications/Adobe Dreamweaver CS4/Adobe Dreamweaver CS4.app/Contents/Frameworks/AdobeOwl.framework/Resources/AuthPlayLib.bundle/Contents/MacO S/AuthPlayLib. One of the two will be used. Which one is undefined.
Mar 30 15:28:34 /Library/Application Support/FLEXnet Publisher/Service/11.5.0/FNPLicensingService[891]: Started - This service performs licensing functions on behalf of FLEXnet enabled products.
Mar 30 15:28:57 com.apple.WebKit.PluginAgent[782]: Debugger() was called!
Mar 30 15:29:33: --- last message repeated 2 times ---
Mar 30 15:29:33 [0x0-0x47047].com.adobe.dreamweaver-10.0[887]: Dreamweaver(887,0xa0aae4e0) malloc: *** error for object 0x333e5dc0: pointer being freed was not allocated
Mar 30 15:29:33 [0x0-0x47047].com.adobe.dreamweaver-10.0[887]: *** set a breakpoint in malloc_error_break to debug
Mar 30 15:29:33 Dreamweaver[887]: Dreamweaver(887,0xa0aae4e0) malloc: *** error for object 0x333e5dc0: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Mar 30 15:29:57 [0x0-0x49049].com.adobe.dreamweaver-10.0[912]: objc[912]: Class ApolloPasteboardSource is implemented in both /Applications/Adobe Dreamweaver CS4/Configuration/Flash Player/AuthPlayLib.bundle/Contents/MacOS/AuthPlayLib and /Applications/Adobe Dreamweaver CS4/Adobe Dreamweaver CS4.app/Contents/Frameworks/AdobeOwl.framework/Resources/AuthPlayLib.bundle/Contents/MacO S/AuthPlayLib. One of the two will be used. Which one is undefined.
Mar 30 15:29:58 /Library/Application Support/FLEXnet Publisher/Service/11.5.0/FNPLicensingService[916]: Started - This service performs licensing functions on behalf of FLEXnet enabled products.
Mar 30 15:30:20 Dreamweaver[912]: Dreamweaver(912,0xa0aae4e0) malloc: *** error for object 0x32bb42f0: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Mar 30 15:30:20 [0x0-0x49049].com.adobe.dreamweaver-10.0[912]: Dreamweaver(912,0xa0aae4e0) malloc: *** error for object 0x32bb42f0: pointer being freed was not allocated
Mar 30 15:30:20 [0x0-0x49049].com.adobe.dreamweaver-10.0[912]: *** set a breakpoint in malloc_error_break to debug
Mar 30 15:30:37 [0x0-0x4a04a].com.adobe.dreamweaver-10.0[942]: objc[942]: Class ApolloPasteboardSource is implemented in both /Applications/Adobe Dreamweaver CS4/Configuration/Flash Player/AuthPlayLib.bundle/Contents/MacOS/AuthPlayLib and /Applications/Adobe Dreamweaver CS4/Adobe Dreamweaver CS4.app/Contents/Frameworks/AdobeOwl.framework/Resources/AuthPlayLib.bundle/Contents/MacO S/AuthPlayLib. One of the two will be used. Which one is undefined.
Mar 30 15:30:37 /Library/Application Support/FLEXnet Publisher/Service/11.5.0/FNPLicensingService[946]: Started - This service performs licensing functions on behalf of FLEXnet enabled products.
Mar 30 15:34:58 osascript[1018]: Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: dlopen(/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found. Did find:\n /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: no matching architecture in universal wrapper
Mar 30 15:35:03 com.apple.backupd-auto[1012]: Not starting scheduled Time Machine backup - time machine destination not resolvable.
Mar 30 15:35:48 osascript[1033]: Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: dlopen(/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found. Did find:\n /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: no matching architecture in universal wrapper
Mar 30 15:35:58 Dreamweaver[942]: Dreamweaver(942,0xa0aae4e0) malloc: *** error for object 0x3332c4b0: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Mar 30 15:35:58 [0x0-0x4a04a].com.adobe.dreamweaver-10.0[942]: Dreamweaver(942,0xa0aae4e0) malloc: *** error for object 0x3332c4b0: pointer being freed was not allocated
Mar 30 15:35:58 [0x0-0x4a04a].com.adobe.dreamweaver-10.0[942]: *** set a breakpoint in malloc_error_break to debug

If you are trying to report a bug, this is not the place for it. This is a user to user Forum. Bug reports go here: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
If you are giving a heads-up to fellow Mac Users, so be it.
If you are trying to get support to extricate yourself from what looks like a really aggravating problem, go to http://www.adobe.com/support/contact/ and choose your favorite means of conversation with Adobe Support personnel.
Beth

Similar Messages

Css Tabs in Dreamweaver CS4 Workspace bug?/annoyance

Css Tabs in Dreamweaver CS4 Workspace. This is probably more
of an
annoyance than a bug.
When working with CSS, I use multiple CSS files and when I
make a change
to one, I hit save (CTRL S)but it doesn't save the CSS file I
was just
working on. In order to make it save that CSS file, I have to
click on
one of the others and then back to the one I was just working
on and
then hit save.
Kind of annoying, right?
I demand this to be fixed! ;)

Art,
I guess you didn't understand what I meant by "focus". Let me
try to
explain in terms of your recipe -- all you need is a slight
change in
workflow:
> 1. Open page with multiple style sheets applied
> 2. Have split screen
> 3. click on one style sheet and edit it anywhere. After
editing, the
> rounded box will be black and have an asterisk applied
At this point, the style sheet has "focus", so click Ctrl+S
now, before
you click back in Design View (which changes the "focus" back
to the
main document).
FYI, if you're clicking in Design View to update the
rendering, you can
hit F5 to update the main document rendering without giving
it "focus".
> 4. Click back to page in design view.
> 5. Click control save. It doesn't save the style sheet
that is
> highlighted and has an asterisk.
> 6. In order to save you must "save all" or click off
and then on
> to the style sheet.
Hope this helps,
Randy
Art wrote:
> Let me restate the problem so it's clear what is
happening.
>
> 1. Open page with multiple style sheets applied
> 2. Have split screen
> 3. click on one style sheet and edit it anywhere. After
editing, the
> rounded box will be black and have an asterisk applied
> 4. Click back to page in design view.
> 5. Click control save. It doesn't save the style sheet
that is
> highlighted and has an asterisk.
> 6. In order to save you must "save all" or click off and
then on to the
> style sheet.
>
> Perhaps this is more an issue of focus rather than a
function of the
> save command.
>
> Since it's not saving, perhaps Dreamweaver shouldn't be
displaying the
> black rounded box as it is no longer selected when you
click back into
> Design view.
>
> Of course there are ways around this; it's just a little
annoying that
> it's displaying "active" yet it's not.

What are common HTML bugs generated by Dreamweaver CS4 itself?

When a link works in browser but fails on server where do you start looking for the cause of problem and its possible solution? What are some of the common HTML bugs that are often generated by Dreamweaver CS4 itself? What are some of dos and don'ts when you are making corrections in the code page? Thank you for your response.

When a link works in browser but fails on server where do you start looking for the cause of problem and its possible solution? What are some of the common HTML bugs that are often generated by Dreamweaver CS4 itself? What are some of dos and don'ts when you are making corrections in the code page? Thank you for your response.

BUG!!! Dreamweaver CS4

This is a BAD BUG, but hopefully you save ALL of your work
prior to testing in Live View. Because if you have a JavaScript,
that you messed up and there is an endless loop, you have to FORCE
QUIT Dreamweaver CS4 (
) and lose the unsaved data since there is NO WAY to
end LIVE VIEW
Below is a sample of code to create the bug for yourself.
Note: You can see I threw the comment code in front of every
line so the message board wouldn't see it as a valid code. And then
launch the faulty code, causing anyone reading this message to
FORCE QUIT their browser.
//<script type = "text/javascript">
// //[CDATA[
// //Warning: this program has a deliberate
// // error! You will have to stop the browser
// // to end the loop.
// i = 0;
// j = 0;
// while (i < 10) {
// j++;
// alert(j);
// } // end while
// //]]>
// </script>

prolights wrote:
> This is a BAD BUG, but hopefully you save ALL of your
work prior to testing in
> Live View. Because if you have a JavaScript, that you
messed up and there is an
> endless loop, you have to FORCE QUIT Dreamweaver CS4 (
) and lose the
> unsaved data since there is NO WAY to end LIVE VIEW
>
> Below is a sample of code to create the bug for
yourself.
>
> Note: You can see I threw the comment code in front of
every line so the
> message board wouldn't see it as a valid code. And then
launch the faulty code,
> causing anyone reading this message to FORCE QUIT their
browser.
>
> //<script type = "text/javascript">
> // //[CDATA[
> // //Warning: this program has a deliberate
> // // error! You will have to stop the browser
> // // to end the loop.
> //
> // i = 0;
> // j = 0;
> //
> // while (i < 10) {
> // j++;
> // alert(j);
> // } // end while
> // //]]>
> // </script>
If browsers barf on it, how is Dreamweaver going to be able
to handle it
any differently?
Submit your bug report here:
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
I just found this:
http://bugs.adobe.com/ its a
shame Dreamweaver isn't
in this system.
Dooza

Image Map Bug in Dreamweaver CS4

I've included a video sample of Dreamweaver's inability to
draw polygonal hotspots in Design view on an image map. The image
is inside an absolutely positioned div tag. After clicking the
first corner, the drawing tool is deactivated. A second click to
create the next corner point selects the underlying image.
In this video sample, I'm using Dreamweaver CS4 on a MacBook
Pro with a 2.4 GHz Intel processor and OS X 10.5.6. The image is
actually a transparent PNG. I'm very careful to click on an opaque
area, but that shouldn't make a difference.
The workaround is to open the image in a blank HTML file,
create the polygonal hotspots there and then copy and paste the
code back into the original HTML page. Adobe should really consider
fixing this.
The video can be viewed here:
http://www.youtube.com/watch?v=tRZGUi53PbI

Good review, David. Thanks for the analysis!
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"David Powers" <[email protected]> wrote in message
news:gqdp6t$70c$[email protected]..
> Murray *ACE* wrote:
>> Or whether it is an issue. For example, the fact
that others are not
>> able to reproduce the problem doesn't bode well in
that regard....
>
> I've just been reading the comments on the CS3 Livedocs
about the same
> problem. Two things stood out: the problem seems to
arise when the image
> is inside a div, and several people said the answer was
to create the
> image map in a new page. Being inside a div should not
present a problem,
> because all my tests have used an image directly inside
a div.
>
> What interested me was that there was no problem
creating an image map in
> a new page. Dreamweaver uses JavaScript in the
background to run a lot of
> its functionality. If there are any errors in the
underlying code, or if
> the code is complex, Dreamweaver can't analyze the page
properly. Another
> possible cause of problems is insufficient memory. If
you have the minimum
> RAM, but other programs are running, this is likely to
cause Dreamweaver
> to fail to function correctly, particularly on large,
complex pages.
>
> So, if Dreamweaver fails to create a hotspot on an
existing page, try it
> on a new page. If it works in the new page, it sounds as
though it's a
> problem with the complexity of the page and/or memory.
If it fails to work
> on the new page, it's back to square one. :(
>
> --
> David Powers
> Adobe Community Expert, Dreamweaver
>
http://foundationphp.com

Is this the right replace to report a bug in dreamweaver CS4?

if so,
i have noticed that when using dreamweaver cs4
on windows vista business(build 6001) with multiple monitors
and dreamweaver is open on a screen that is not the primary screen
the tooltip box (that comes up when entering a function name and gives details on the parameters) that should appear above and right of the mouse location appears to stretch in the direction of the primary screen, and you cannot see the text that should be inside it.
see screenshot

To report bugs or suggest improvements:
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Dreamweaver CS4 Search Folder Bug (?)

Just curious if anyone else has this issue:
When doing a search and wanting to only focus on a specific folder within the root, I have to go one folder deeper to have Dreamweaver select the folder I actually want.
For example, if I want to search files within /root/main/ I have to actually select /root/main/subfolder/ to have Dreamweaver actually search the "main" folder.
Is this a bug or just how the search folder works?
Dreamweaver CS4 (10.0 build 4117) for Windows 7

It's a well-known issue. See http://forums.adobe.com/thread/478327.

Fix Dreamweaver CS4 Color Eyedropper Bug

Dreamweaver locks up when using the eyedropper from the CSS
panel to select/match a color from any object in Design view.
Easiest to explain by describing a split view. Dreamweaver locks
every time -- when placing cursor in a background color code in a
style sheet, then going to the CSS panel and selecting the
background color swatch for that style, then with the eyedropper,
touching a color in the Design view part of the split screen.
Dreamweaver CS3 never locked up when performing these same
steps. Dreamweaver CS4, locks up whether selecting a color in a
bitmap or a CSS background color that is displayed in the Design
split view. Means I have to go to Fireworks to color match, and if
the color I want is in a range of a gradient, I have to make the
gradient a bitmap before selecting the spot with the eyedropper. I
even had some difficulty in Fireworks, as the selection wouldn't
show up in the color panel when I touched the bitmap with the
eyedropper. I could see the color code in the popup color selector
and clicked there for the color to show up in Fireworks' color
panel.
Kind of a hassle...would be nice to get an update fix for
this.

prjviera wrote:
> Dreamweaver locks up when using the eyedropper from the
CSS panel to
> select/match a color from any object in Design view.
This is a user-to-user forum. If you have found what you
believe to be a
bug, please file an official report giving as many details as
possible
to reproduce it. The official report form is here:
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS4",
"PHP Solutions" & "PHP Object-Oriented Solutions"
http://foundationphp.com/

Dreamweaver CS4 has stopped working

*** Bug Report ***
"Dreamweaver crashes when trying to open it."
April 19th - 8:00 PM
Reproduce Error:
Launch Dreamweaver CS4 from start menu.
What happens:
Does not load.
Error message appears:
Notes:
Has been working fine for past 3 days.
Errors occured today at random, without reason.
Reporting from a system that has been reformatted one week ago, fresh install of Windows Vista Ultimate with latest updates & service packs.
Dreamweaver CS4 installed along with the Master Suite Collection, other software function just fine.
System Specs:
AMD Athlon 64 X2 Dual Core Processor 5600+ 2.80 GHz
4.00 GB Memory (RAM)
500 GB Storage
Windows Vista 64-bit
Additional Notes:
I have had previous peril with Fireworks CS4 earlier this week crashing and had to take valuable time researching the problem. Happened to be one font out of three thousand that I have readily available for my needs. This new problem with Dreamweaver has further disappointed me and I need to use the software I purchased as soon as possible. I have taken the time to send in a bug report, as well as post this thread.
Please guide me in a safe & proper procedure to determine the cause of the crash. Thank you.
Sean

Jhfras wrote:
Nadia
Renaming the Configuation folder and then opening Dreamweaver worked like a charm. I was ready to give up on CS4 and I had already gone back to using DW 8. Thank you for sharing- don't think I would have ever solved this without your help. That is what sharing is all about.
You're welcome :-)
Nadia
Adobe® Community Expert : Dreamweaver
Unique CSS Templates | Tutorials | SEO Articles
http://www.DreamweaverResources.com
Web Design & Development
http://www.perrelink.com.au
http://twitter.com/nadiap

Unable to Uninstall Photoshop CS4 and Dreamweaver CS4

it's been a couple of days since i tried out Photoshop CS4 and Dreamweaver CS4 to see how they compare to the CS3 versions, it worked fine and all till suddenly it stopped working, so i been trying to uninstall/reinstall to get it working under the free trial limit i still have left (27 days as of this writing) it still will not work.
Sometimes i would install Photoshop/Dreamweaver and say an error occurred and some components were unable to install and would be unable to load the file even after doing what the instructions say...
Same goes for when i try to uninstall both Photoshop/Dreamweaver, i would try to uninstall and would still remain in my program files...
I am completely stumped on what to do, i can't even re-install photoshop/dreamweaver cs3 as well due to this...
I am running on Vista 32bit SP1 Pack on HP Pavilion, i want to completely get rid of CS4 versions and go back to my reliable CS3 again, any help please would be greatly appreciated.
Kantori

John... if you read what I said you would of caught that i did do it:
"did what was suggested, worked like a charm for the CS3 and Dreamweaver CS4 but although it did work on Photoshop CS4. it did something i was dumbfounded to see, it did something odd in which it took out the Uninstall/Change tab option for removing programs (I was viewing it to see if it uninstalled completely) also it brought out a bunch of programs that weren't in that section before and was unable to uninstall/remove them.
So i had to do a system restore point to go back and try again. After doing it two more times (ya two!) still doesn't work, i am 7 hours into trying to resolve this... sigh. "
At that time i said i had done it 2 times, 3 in total, i am on try #6 all with the same results with the exact after effects once i restart my PC.
Here's what it does to tell what goes on:
1) after installing microsoft's cleaner then opening up the cs4 cleaner under admin, it does its thing, it asks me if i wish to remove Flash Player 10 after choosing remove Photoshop CS4, now here i done both remove Flash Player and not remove it with the same results, losing the uninstall/change option on the control panel, which frustrates me.
2) After seeing that i try to install Photoshop CS4 again, once its done, i open it up, try to go to the trial option where as i stated previously says there's an error and can't open the trial page which would open up Photoshop completely but since it can't i cannot go beyond that window.
3) So ya... i try ONCE again to do it all over after restarting and SAMETHING! no uninstall/change option appearing and unable to open up Photoshop CS4 in which i resort to doing a system restore again and trying once more.
NOW, one would think that after the first 3 times it should be working properly, i mean I thought it would after removing both Photoshop CS3 and Dreamweaver CS4 it's bound to do the same for Photoshop CS4, but it doesn't completely create a "FREASH" install. It's like it still remembers what messed up functions it still had and what's up with it removing the uninstall/change option? that just bogles my mind.
i tried many things, re-downloading the trial from adobe, etc i never would of thought just one program could cost me so much wasted time just to get it working and it's a free trial nonetheless so excuse me John Joslin if your remark kind of bugs me, I need some assistance/advice on trying to correct this problem, not a
"It should have done!
Run it a few times. "
comment that's already common knowledge for me in what I have already been doing long before your post.

Dreamweaver cs4 not responding

Hi,
I have just installed CS4 on my work computer which has a Windows OS.
I am finding that when I open files in Dreamwever from the local site, i get a "not responding" message from the task manager and the files take 1-2 mins to open.
Even moving between open *.xhtml files takes 1-2 mins!
I have followed advice on some adobe support pages and upped the page file size, performed a disk cleanup, recreated the Configuration folder in my profile version of Dreamweaver CS4, installed all the latest updates - with no luck
The local version of the site is quite large with over 350 files.
In the Dreamweaver site conifig have also attempted turning of the site cache and removing the remote server setup. (also turned off the check in/out feature)
This did not help either.
The local version of this site is on a network server which is accessed via a mapped drive on my pc - this requires a username and password when i first connect to it, but after the initial connection it does not prompt me again.
I have another local site with files stored on my C: drive which i have no problem opening whatsoever.
Can anyone pleeeeeease help!
This is preventing me from working in Dreamweaver at all....
The next alternative for me is to copy the local site files to my pc for working on - which is really not a good idea as it is not backed up.
any advice would be appreciated!

Thanks Jon very much for your suggestion.
I work on a Macintosh iMac with a 2.16 GHz Intel Core 2 Duo running on 2GB 667 MHz memory. I am running no extensions on Dreamweaver.!
I usually pull down any files from my clients' servers then work on the files locally. Once I am happy that the files have been altered appropriately I then send them back up to the server.
Up till now the files have worked relatively well although they can take a little while to load. I notice that if I view the files in code only there is no problem but since I am fundamentally a designer I like to see what it is I am doing and tend to avoid working with the files in code.
I have done exactly what you have suggested although I have done that before thinking it would 'clear out' the system. Sadly, despite my meticulous attention to removing all the files associated with Dreamweaver the problem still persists.
There are some points to note in all this. While trying to pin down the problem I have noticed that it is the larger file sizes that jam Dreamweaver BUT it is a relative problem. Big files on one of the clients sites are small files on other client sites - one minute it will not open a 50k file for one client the next it will be a 372k file on another site that stalls!
It is interesting just how many people there are out there having the same issues that I appear to be having.
Thanks for all your help
If I come up with a solution I'll let you know.

Problem with Dreamweaver CS4 after upgrade to Lion

I am having a problem after upgrading to Lion, with my Dreamweaver CS4 . When I try to use the bold button the text completely dissapears from the screen in design view The text is still there as it shows up in preview and also shows up in code view. Has anyone else had similar problems since the upgrade? and is there going to be a fix for it.

http://www.adobe.com/products/creativesuite/faq.html#lion-os
There are a number of known compatibility issues with Creative Suites and Lion
http://kb2.adobe.com/cps/905/cpsid_90508.html
Can't see your specific issue mentioned though.
Perhaps report it to Adobe via the Bug Report form giving full details
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Will Dreamweaver CS4 work properly with 10.6.1 Snow Leopard?

Hello
Can anyone tell me please, if Adobe Dreamweaver CS4 work properly with my MacBook OS 10.6.1 Snow Leopard? Adobe state "Mac OS X v10.4.11–10.5.4" in the system requirements, but does this mean, in practise, that Dreamweaver will not work properly with Snow Leopard?
I have tried to find info about this here, but have spend ages wading through masses of complaints about various applications crashing for people after they upgraded to 10.6.1 Snow Leopard. Personally, touch wood, I've had no problems with Snow Leopard, but I only really use it for Internet surfing and word processing (my work, music stuff on Logic Pro 8, is done on my Mac Pro which came with Leopard and which I am NOT upgrading - not yet!).
I have also attempted to get an answer from Adobe - I 'phoned their "Pre-sales enquiries" number 0800 028 0148 (in the UK) and spoke to someone who sounded as if she was on the moon and who clearly had absolutely no idea what I was talking about. I gave up with them! They didn't give an email address to ask on.
I'd be very grateful if anyone can give a clear, authoritative answer please - if possible.

I've been a Mac user since 1987 and have never upgraded the OS too soon after a new version was launched. Any new OS, like new houses, will have a 'snagging list' - unforeseen problems that arise and need to be sorted before your purchase is truly habitable and functions as expected.
But the stability of OS X 10.5 paved the way for my lapse of judgement when I upgraded to Snow Panther last week, while its compatibility with some major software is still clearly too buggy.
I've been using Dreamweaver (DW) CS4 successfully on OS X 10.5 for some time. Since installing OS X 10.6.1 I now have problems with DW, which I've alerted Adobe to.
When using Design View in DW CS4, any formatted text - from html tags to css tags - disappears from the Design view. The code appears correctly in the Code window and even if you highlight text that has coding attached in Code view - eg text with a url link attached - the Design view continues to ignore it and removes the text from its view. I've discovered that my heading tags (h1, h2, etc) all make the text disappear in Design view in a way that would be the envy of members of the Magic Circle! The only thing that seems to get through is text that is surrounded by paragraph tags.
Thing is that 'Preview in Browser' shows the page correctly (except in Opera, which I've only installed since installing Snow Leopard, so I can't say how this displayed in the previous OS versions).
Also when I upload the site to the server it all seems to display more or less as it should.
So currently it seems that DW CS4's Design view is no longer WYSIWYG! Expect to find lots of text hidden in Design view and have to use Code view much more.
It would be nice to think that Apple and Adobe would talk to each other and work it out between them.
re: Dreamweaver, I'd check back to Adobe.com regularly to see when they upgrade the OS requirements to 10.6.1 (I hadn't spotted before I bought Snow Leopard that they only go up to 10.5 in their OS recommendations).
My advice if you're thinking of upgrading to Snow Panther: delay it until it more of it works compatibly with your major applications. Check the OS spec from each software manufacturer first. Meanwhile I'll just have to wait patiently for Apple & Adobe to get their act together...
Message was edited by: bcmartin

How to Make Dreamweaver CS4/Flash CS4 Website Function on all Latest Mobile Devices

Hello!
I am trying to add code into my Dreamweaver CS4 file and/or Flash CS4 file in order to have the website I have created work across all of the latest mobile devices as well as traditional online systems. My flash file has a transparent stage, and my dreamweaver file has a full-screen background image. I have reviewed various tutorials and articles available online, and some advocate simply adding code, which does not seem to be working for me, while others suggest having a similar separate site created solely for mobile devices. If this is the best option, I don't know how that should be set up. What is the best path to take with this?
This is the collection of various pieces of code I have tried adding to my files:
<meta name="viewport" content="width=device-width" user-scalable="yes" initial-scale="1.0" /> 
   <meta name="HandheldFriendly" content="true" /> 
</style>
   <param name="allowScriptAccess" value="sameDomain" />
      <param name="allowFullScreen" value="true" />
<param name="allowScriptAccess" value="sameDomain" />
        <param name="allowFullScreen" value="true" />
        <param name="var params = {          id: "flashID", name: "flashcontent", menu: "false", allowFullScreen: "true", fullScreenOnSelection: "true", scale:"noscale", salign:"middle"};"
stage.scaleMode = StageScaleMode.NO_SCALE;
stage.align = StageAlign.TOP_LEFT;
//or//
this.stage.scaleMode = StageScaleMode.NO_SCALE;
this.stage.align = StageAlign.TOP_LEFT;
next_btn.width = 133 * .5;
next_btn.height = 133 * .5;
//flash//
next_btn.width = Capabilities.screenDPI * .5;
next_btn.height = Capabilities.screenDPI * .5;
//flash//
this.stage.addEventListener(Event.RESIZE, doLayout);
//flash://
<initialWindow>
   <width>320</width>
   <height>480</height>
   
</initialWindow>
* Convert inches to pixels.
private function inchesToPixels(inches:Number):uint
   return Math.round(Capabilities.screenDPI * inches);
var button:Sprite = new Sprite();
button.x = 20;
button.y = 20;
button.graphics.beginFill(0x 003037);
button.graphics.drawRect(0, 0, this.inchesToPixels(.75),
   this.inchesToPixels(.25));
button.graphics.endFill();
   this.addChild(button);
//hard-code title://
var titleBar:Sprite = new Sprite();
titleBar.x = 0;
titleBar.y = 0;
//stage width determines width of title://
var titleBar:Sprite = new Sprite();
titleBar.x = 0;
titleBar.y = 0;
titleBar.graphics.beginFill(0x003037);
titleBar.graphics.drawRect(0, 0, this.stage.stageWidth,
   this.inchesToPixels(.3));
titleBar.graphics.endFill();
this.addChild(titleBar);
//footer://
var footer:Sprite = new Sprite();
footer.graphics.beginFill(0x003037);
footer.graphics.drawRect(0, 0, this.stage.stageWidth,
   this.inchesToPixels(.3));
footer.graphics.endFill();
footer.x = 0;
footer.y = this.stage.stageHeight - footer.height;
this.addChild(footer);
* Center one DisplayObject relative to another.
private function center(foreground:DisplayObject,
   background:DisplayObject):void
      foreground.x = (background.width / 2) -
         (foreground.width / 2);
      foreground.y = (background.height / 2) +
         (foreground.height / 2);
//cont.//
var title:SimpleLabel = new SimpleLabel("My Application",
   "bold", 0xffffff, "_sans", this.inchesToPixels(.15));
this.center(title, titleBar);
this.addChild(title);
//override width and height getters
public override function get width():Number
   return this.textLine.textWidth;
public override function get height():Number
   return (this.textLine.ascent - 1);
if (Capabilities.manufacturer == "Android Linux" && Capabilities.screenResolutionY == 1024)
next_btn.width = 85;
next_btn.height = 85;
This is the code for my Dreamweaver CS4 file (without the additional erogenous code attempts):
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<?xml version="1.0" encoding="utf-8"?><!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.2//EN"
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>My Website Title and Slogan.</title>
<style type="text/css">

<script src="Scripts/swfobject_modified.js" type="text/javascript"></script>
</head>
<body>
<img src ="image.gif" width=90% height=auto>
<script src="Scripts/swfobject_modified.js" type="text/javascript"></script>
<meta name="Keywords" content="keywords…" />
<div align="center"></div>
<div align="center">
<p> </p>
<p>
    <object id="FlashID" classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="900" height="630">
      <param name="movie" value="FlashFile.swf" />
      <param name="quality" value="high" />
      <param name="wmode" value="transparent" />
      <param name="swfversion" value="6.0.65.0" />
      
      <param name="expressinstall" value="Scripts/expressInstall.swf" />
      
      
      <object type="application/x-shockwave-flash" data="FlashFile.swf" width="900" height="630">
        
        <param name="quality" value="high" />
        <param name="wmode" value="transparent" />
        <param name="swfversion" value="6.0.65.0" />
        <param name="expressinstall" value="Scripts/expressInstall.swf" />
        
        <div>
          <h4>Content on this page requires a newer version of Adobe Flash Player.</h4>
          <p><a href="http://www.adobe.com/go/getflashplayer"><img src="http://www.adobe.com/images/shared/download_buttons/get_flash_player.gif" alt="Get Adobe Flash player" width="112" height="33" /></a></p>
        </div>
        
      </object>
      
    </object>
</p>
</div>
<div align="center"> </div>
<script type="text/javascript">

</script>
</body>
</html>
I have tried various combinations of the code listed above, but nothing seems to be working. I am not sure as to the positioning of the code, and maybe that is the problem, or maybe it is because this code in not for CS4, or not appropriate for my project. I also do not know what code should be inside the Flash file, nor what should should be inside the Dreamweaver file.
Thank you in advance for any assistance!

Hi
To add to what Gramps has said, Adobe has ceased developing its flash player for ALL mobile devices so do not use Flash for any mobile device.
Depending on the complexity of your Flash program you may be able to recreate it using Edge, but the code generated by Edge does not work in IE8 or below.
For details on Edge, see - http://labs.adobe.com/technologies/edge/
PZ

How to Make Flash CS4/Dreamweaver CS4 Website Function on all Latest Mobile Devices

Hello!
I am trying to add code into my Dreamweaver CS4 file and/or Flash CS4 file in order to have the website I have created work across all of the latest mobile devices as well as traditional online systems. My flash file has a transparent stage, and my dreamweaver file has a full-screen background image. I have reviewed various tutorials and articles available online, and some advocate simply adding code, which does not seem to be working for me, while others suggest having a similar separate site created solely for mobile devices. If this is the best option, I don't know how that should be set up. What is the best path to take with this?
This is the collection of various pieces of code I have tried adding to my files:
<meta name="viewport" content="width=device-width" user-scalable="yes" initial-scale="1.0" /> 
   <meta name="HandheldFriendly" content="true" /> 
</style>
   <param name="allowScriptAccess" value="sameDomain" />
      <param name="allowFullScreen" value="true" />
<param name="allowScriptAccess" value="sameDomain" />
        <param name="allowFullScreen" value="true" />
        <param name="var params = {          id: "flashID", name: "flashcontent", menu: "false", allowFullScreen: "true", fullScreenOnSelection: "true", scale:"noscale", salign:"middle"};"
stage.scaleMode = StageScaleMode.NO_SCALE;
stage.align = StageAlign.TOP_LEFT;
//or//
this.stage.scaleMode = StageScaleMode.NO_SCALE;
this.stage.align = StageAlign.TOP_LEFT;
next_btn.width = 133 * .5;
next_btn.height = 133 * .5;
//flash//
next_btn.width = Capabilities.screenDPI * .5;
next_btn.height = Capabilities.screenDPI * .5;
//flash//
this.stage.addEventListener(Event.RESIZE, doLayout);
//flash://
<initialWindow>
   <width>320</width>
   <height>480</height>
   
</initialWindow>
* Convert inches to pixels.
private function inchesToPixels(inches:Number):uint
   return Math.round(Capabilities.screenDPI * inches);
var button:Sprite = new Sprite();
button.x = 20;
button.y = 20;
button.graphics.beginFill(0x 003037);
button.graphics.drawRect(0, 0, this.inchesToPixels(.75),
   this.inchesToPixels(.25));
button.graphics.endFill();
   this.addChild(button);
//hard-code title://
var titleBar:Sprite = new Sprite();
titleBar.x = 0;
titleBar.y = 0;
//stage width determines width of title://
var titleBar:Sprite = new Sprite();
titleBar.x = 0;
titleBar.y = 0;
titleBar.graphics.beginFill(0x003037);
titleBar.graphics.drawRect(0, 0, this.stage.stageWidth,
   this.inchesToPixels(.3));
titleBar.graphics.endFill();
this.addChild(titleBar);
//footer://
var footer:Sprite = new Sprite();
footer.graphics.beginFill(0x003037);
footer.graphics.drawRect(0, 0, this.stage.stageWidth,
   this.inchesToPixels(.3));
footer.graphics.endFill();
footer.x = 0;
footer.y = this.stage.stageHeight - footer.height;
this.addChild(footer);
* Center one DisplayObject relative to another.
private function center(foreground:DisplayObject,
   background:DisplayObject):void
      foreground.x = (background.width / 2) -
         (foreground.width / 2);
      foreground.y = (background.height / 2) +
         (foreground.height / 2);
//cont.//
var title:SimpleLabel = new SimpleLabel("My Application",
   "bold", 0xffffff, "_sans", this.inchesToPixels(.15));
this.center(title, titleBar);
this.addChild(title);
//override width and height getters
public override function get width():Number
   return this.textLine.textWidth;
public override function get height():Number
   return (this.textLine.ascent - 1);
if (Capabilities.manufacturer == "Android Linux" && Capabilities.screenResolutionY == 1024)
next_btn.width = 85;
next_btn.height = 85;
This is the code for my Dreamweaver CS4 file (without the additional erogenous code attempts!):
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<?xml version="1.0" encoding="utf-8"?><!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.2//EN"
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>My Website Title and Slogan.</title>
<style type="text/css">

<script src="Scripts/swfobject_modified.js" type="text/javascript"></script>
</head>
<body>
<img src ="image.gif" width=90% height=auto>
<script src="Scripts/swfobject_modified.js" type="text/javascript"></script>
<meta name="Keywords" content="keywords…" />
<div align="center"></div>
<div align="center">
<p> </p>
<p>
    <object id="FlashID" classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="900" height="630">
      <param name="movie" value="FlashFile.swf" />
      <param name="quality" value="high" />
      <param name="wmode" value="transparent" />
      <param name="swfversion" value="6.0.65.0" />
      
      <param name="expressinstall" value="Scripts/expressInstall.swf" />
      
      
      <object type="application/x-shockwave-flash" data="FlashFile.swf" width="900" height="630">
        
        <param name="quality" value="high" />
        <param name="wmode" value="transparent" />
        <param name="swfversion" value="6.0.65.0" />
        <param name="expressinstall" value="Scripts/expressInstall.swf" />
        
        <div>
          <h4>Content on this page requires a newer version of Adobe Flash Player.</h4>
          <p><a href="http://www.adobe.com/go/getflashplayer"><img src="http://www.adobe.com/images/shared/download_buttons/get_flash_player.gif" alt="Get Adobe Flash player" width="112" height="33" /></a></p>
        </div>
        
      </object>
      
    </object>
</p>
</div>
<div align="center"> </div>
<script type="text/javascript">

</script>
</body>
</html>
I have tried various combinations of the code listed above, but nothing seems to be working. I am not sure as to the correct positioning of the code, and maybe that is the problem, or maybe it is because this code in not for CS4, or not appropriate for my project. I also do not know what code should be inside the Flash file, nor what should should be inside the Dreamweaver file.
Thank you in advance for any assistance!

There is no simple code to add that will display the same on all mobile devices....
you do know that the iProducts (iPhone, iPad, etc) don't display Flash at all, right?
So as a start for "functioning on all latest mobile devices" you should drop any Flash content you have and move on.
Adninjastrator

Dreamweaver CS4 attempted to free unallocated memory bug

Similar Messages

Maybe you are looking for