Repeated crashing

[Penhome]

Hi All
I'm working with a designer to create a new site in V11 Business and am still learning the ropes with Actinic having used Frontpage/Dreamweaver for the last 15 years on my current site. So apologies if this is a daft question.
Actinic keeps crashing (or 'not responding') whether on the trial version (with TVs and Digital Cameras) or on the snapshot site my designer has sent me.
Everything loads up fine, and I can see all the products down the left, but Actinic repeatedly either crashes within 4-5 clicks on the products and generates a dump report or 'fails to respond' and the screen greys out.
I've uninstalled/reinstalled Actinic and compacted the databases, but this doesn't make any difference.
I've tried Actinic both on a new ACER running Windows 7 Professional and on another new ACER running Windows Home Premium, both with 3gb RAM, but the crash scenario is the same on both machines.
I feel I must be doing something wrong, but can't work out what!
Help!

Simon

[NormanRouxel]

Welcome to the Community, Simon.

I'm afraid to say that what you're experiencing isn't normal behaviour. If it was, the forum would be swamped with posts identical to yours. So I can only give general advice.

Things to consider being suspect is your internet browser and network connection (which is the only thing I can think of that would be common to 2 different PC's). Actinic uses IE internally for the previews and often needs an Internet connection to load some external JavaScripts.

Also check if you use any kind of real-time backup or anti-virus scanning as this may be conflicting with Actinic.

Maybe others will be along soon with alternative ideas.

[Penhome]

Norman
Many thanks for the advice.
The ACER machines have up-to-date IE as the browser and a fairly high speed broadband wireless connection. I haven't any real-time backup but these machines both have McAfee antivirus and firewall running. I'll try turning this off in the morning and see what happens.
Thanks again.

Simon

[NormanRouxel]

Forgot to ask. What is the exact version of Actinic (e.g. 11.0.1) that you're using?

[Penhome]

It was 11.0.1 on one machine and then 11.0.2 on the second. The crashing regime was identical. I'll see whether turning off McAfee has any effect in the morning.

[ton]

Anything like this: http://community.actinic.com/showthread.php?t=51454

If you change the resolution down to the lowest possible setting does it crash, try it ( mind you impossible to work in such a low resolution)

TON

[Penhome]

Hi Ton
Yes!! This seems to be the same problem!
I've tried taking the screen res down from 1920x1080 to 1600x900 and then 1280x720, but it's still crashing when I do anything with products. It's fine if I alter content pages or click around the main menus.
I also turned McAfee off, but this made no difference.
Windows Updates are all done and installed.
Did thread 51454 end up with any solution? The last post seems to be in February.
Many thanks

[jont]

I had a similar issue with DreamWeaver - tracked this back to an up to date graphics driver as part of a windows update. I deleted and reinstalled from the original disk and all was fine. No software program is perfect and it only takes the smallest of errors and disaster ensues.

It me be worth deleting the contents of the PreviewHTML and DesignPreviewHTML folders.

External calls, iffy jQuery scripts and malformed HTML can all cause crashes within Actinic. Try also turning off the HTML checking. IE browser plug-ins are another source of concern as Actinic uses IE for the inbuilt preview (which still is called whether the preview pane is open of closed)

[Penhome]

Hi Jont
Thanks for the comments, but these are two brand new machines bought just to run Actinic on. All I have done so far is to download Actinic's trial site software (which crashed on both machines) and then have a 5 second look at my designer's snapshot before that crashed. Dreamweaver, my current site and everything else are on an Apple Mac.
So I haven't done any coding (or anything else) on either machine or within Actinic.
This computer seems to have IE versions on it - an IE9 64 bit edition and a non-64 bit version, both 9.0.5. How does Actinic know which to use, or doesn't it make any difference?
Simon

[ton]

I found only the 800x600 resolution worked so even lower than your tried.

In fairness actinic was only very recently in contact with a version for me to try, unfortinatly it didnt work and I had emailed back to say so but there were 2 voicemails on my phone this week from actinic checking up so I reckon they didnt get my email responce. Ive been unavailable all this week so I had resent the email and will ring them on Monday.

TON

[Penhome]

Ton
So can you still not use your new laptop? I've only just bought these two Acer desktops specifically for Actinic as everything I do is on a Mac.
It's about five months since you first posted this problem on the other thread.
Simon

[nileshpa]

It appears I may also be a victim of the notorious repeated crashes.
Started happening about a week ago (v11.0.1). Initial thought was because new products with attributes, components etc were imported. However, DB has been compacted number of times. Can't see anything wrong with these as crashes happens randomly on any product whether new or old. Have raised a call with support and was asked to upgrade to 11.0.2. This was done on Friday but made no difference.

I've now turned off both preview and the details tab. - Still crashes.
Avast was last software added (month ago) - Switch that off & no difference.
Took another Machine, a Dell running Win7 64bit & 8 Gb Ram. Clean install of V11.0.2 with very low resolution and imported the site - Still makes no difference.

Call still open with support. They have a copy of ACD as will as DMP files. Will see what they come up with. At the moment its practically unusable.

Nilesh

[brucet]

Sorry for the problems you have been having. We have been investigating this issue for some time, and we do have a special build available that has solved the problem for several users, though not for all. Please contact support and they can provide you with a copy of this build to try out.

The issue is a composite one, caused by a loophole in the way Windows 64 handles errors in 32-bit applications. It's proving extraordinarily difficult to work around, but we have made a lot of progress and we hope to have a comprehensive solution available soon.