Most probably there is a problem opening the map. CC3+ loads the last map on startup, so if something goes terrible wrong doing that, symptoms like that can manifest.

Easiest way is to make sure all instances of CC3+ are shut down (use task manager to kill them if required, or reboot your computer), then instead of clicking the CC3+ icon to start the program, double click on any map file instead as that will start the program with that map instead (Obviously, don't try to double click on the suspected problematic map, but try something known good, like one of the example files that came with the program)

It does. It is easy to see where the problem lies though. If it crashes while converting the final file, you'll be left with a fully functional temporary bitmap (the filename.bmp.jpg file) that contains the complete export, and if you looked at the export dialog during export, you'll also see that it is done with all the passes over the sheets.

On the other hand, if it crashes while CC3+ is rendering, the temprary bitmap will be corrupted (probably look like a half-finished export), and you'll also notice that the crash happened at the middle of rendering a sheet if you were looking at the export dialog.

ImageMagick is smart enough to use the disk as a cache if needed though, so even the 32-bit version should normally be able to handle any size output CC3+ is capable of producing.

When I try to work out where the problem lies, I often use a series of elimination step. Start by hiding half the sheets and testing, until I have narrowed down which sheet it is on, then do the same for the layers involved on that sheet. Then I start eliminating the entities on the sheet, half at a time.

Often, you can use quicker export options when you narrow down a problem. For example, exporting to bmp skips most of the final conversion step, and you can usually export at a lower resolution and turn off things like antialiasing, or even export without effects on. Just test with reduced export settings first to see if it still crashes, sometimes the conditions are no longer fulfilled for the crash when you do that, but if it still does, then it is no need spending 10 mins on each elimination step when you can spend 30 secs.

As for turning off progressive jpg, I have no idea whatsoever why that would help with anything. That option is used in the final conversion step, i.e. AFTER CC3+ have rendered everything, and have a complete bitmap to convert to jpg, while for me at least, it crashed during the actual rendering step long before that option can affect anything.

I seem to be able to reliably crash it. Did some testing, and seems to be down to building 20. It is right outside the area, but to avoid weird effect clipping at the edges, the render works with a slightly larger area than you select for the export.

Delete the building, and the export should go through. (You'll probably want to redraw it of course, but it is good just testing export once before that to make sure the problem is gone for you)

These lines happens because nodes are placed in such a way that you get very sharp angles on wide lines. There are two main things that can be done:

• Use the SIMPLIFY command. This command removes nodes that are too close together, and might fix the problem. One needs to experiment a bit with the simplification distance to find the best value, as this depends on map size. For larger maps, it may be 1 or more, but for smaller maps, it may just be a small fraction. Save your map before experimenting so you can easily go back to a previous version (Undo also works)
• Stop using entities with a separate outline entity, and use effects instead. Since this problem is connected to wide lines, it doesn't affect the landmass itself, only the outline that has been applied. For example, on the Mike Schley overland, this outline is on the COASTLINE sheet. Hide this sheet, and apply an outer glow to the land instead.