Sorry, but no obvious triggers. Crashes during close-range editing of layouts. It happens about every hour and a half of use. When the program crashes there are two different results- 1) the entire program window disappears quietly with no outward signs or 2) I get the standard XP program abnormal end pop-up that asks if I want to send in an error report to Microsoft.

In either case, all work since the last save is lost. This happened once in a while with version 3.20.2, but more often with version 3.21.0.

So far the most likely cause is the so called undo-buffer.

Every action during a session is recorded, so you can 'undo' your actions all the way back to the initial situation.
All these actions are stored (in an economic way) in the computer's main memory.

So far, we didn't like to restrict the number of recorded actions.
However, after an intensive 1.5 hour session, things might get awkward.
We might reconsider this, and only store the last few hundred actions.

Could you confirm that this happens after a long series of actions during a somewhat longer time?
If not, please take another look at our previous reply.

David.

Hi,

Just had the same experience. System almost totally frozen. Over 1.5 Gb memory going to Anyrail and none free. After waiting over half an hour decided to stop the non-responding programme. Imagine the joy as I glimpsed the full plan update in clear for a fraction of a second before it turned off unsaved.
I am still on 3.19 so I will download 3.21.1 ASAP.

David E 

I'm sorry to report that AnyRail 3.24.2 also crashes from time to time. Several times I have lost the track I had been working on. Also tonight. I was working for approx. half an hour when I got a "Runtime Error" (See attachment for error dialog). I have looked up the error log, it's posted at the bottom of this message.


===========================================
Type gebeurtenis:   Fout
Bron van gebeurtenis:   Application Error
Categorie van gebeurtenis:   Geen
Gebeurtenis-ID:   1000
Datum:      2-4-2009
Tijd:      21:45:00
Gebruiker:      n.v.t.
Computer:   XXXXXXXXXXXXX
Beschrijving:
Vastgelopen toepassing: anyrailnl.exe, versie: 3.24.2.0, vastgelopen module: anyrailnl.exe, versie: 3.24.2.0, vastgelopen op: 0x001db884.

Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp voor meer informatie.
Gegevens:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 61 6e 79   ure  any
0018: 72 61 69 6c 6e 6c 2e 65   railnl.e
0020: 78 65 20 33 2e 32 34 2e   xe 3.24.
0028: 32 2e 30 20 69 6e 20 61   2.0 in a
0030: 6e 79 72 61 69 6c 6e 6c   nyrailnl
0038: 2e 65 78 65 20 33 2e 32   .exe 3.2
0040: 34 2e 32 2e 30 20 61 74   4.2.0 at
0048: 20 6f 66 66 73 65 74 20    offset
0050: 30 30 31 64 62 38 38 34   001db884
0058: 0d 0a                     ..     
===========================================

That's it...

Hope this information helps.

Hello David,

I'm sorry, I can't say that there is a specific action that triggers the crash.
I was just connecting a switch to another piece of track.

Hello Leapfrog,

I'm sorry, but we've not been able to reproduce the problem so far. Are you working with one particular track plan? If so, could you please send it to us?

David.

Hello Leapfrog,

I know it's a while ago, but thanks to a crash report from one of our users, we've found an issue with extensible track after it has been deleted.

Have you been using this extensible track (in Dutch: uitschuifbare rails) in your layout?
In that case, the problem might very well be solved in the next release.

David.

We're solving the issue right now. It's not yet solved in 3.27.0.

David.