LaTeX.org

Hi samson,

The log indicates that there is a problem to write to the file "thesis.dvi":


! I can't write on file `thesis.dvi'.
Please type another file name for output
! Emergency stop.
<to be read again>
\endgroup \set@typeset@protect
l.32 \newpage

*** (job aborted, file error in nonstop ...

It can be two per minute or none in a day. I think that there is some bug in the editor that I tend to hit when I revise texts. For when I'm writing new texts, TXC is quite stable.

Here is my crash statistics for April:

2010-04-01: 2 crashes
2010-04-02: 2 crashes
2010-04-03: 0 crashes (not used)
2010-04-04: 1 crash
2010-04-05: 9 crashes
2010-04-06: 6 crashes

TXC 2.0a2 is quite unreliable with a bigger project (+/- 15 includes, 300 pages).

Please check WER data! (Unsent reports have been sent in the meantime.)
If you like to get feedback on TXC 2.0, you should react to problem reports and provide new builds on a regular basis. There SHOULD be some ...

Here is more feedback from my daily TXC 2a2 use:

- TXC occasionally crashes during compilation.
- During compilation, the TXC process ("TeXnicCenter.exe") creates 20-48% CPU. Since this is on dual core, this means that TXC almost saturates one core! It's closer to 20% if the application window is ...

I also think that compilation is quite slow.

But I want to focus on the crashes. They happen quite often to me. In the last 24 hours I had 4 crashes. They seem to be triggered by a certain sequence of editing commands issued by typing. I cannot say exactly which one. But often it seems to be ...

Third crash; this time I've lost text. grrr.

Name der fehlerhaften Anwendung: TeXnicCenter.exe, Version: 2.0.1071.0, Zeitstempel: 0x4b3bdb1a
Name des fehlerhaften Moduls: ntdll.dll, Version: 6.1.7600.16385, Zeitstempel: 0x4a5bdb3b
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00033185
ID des ...

Please also have a look at WER data which should be obtainable through Microsoft.
TXC crashed for the second time while compiling. WER-reports have been created.

Fehlerbucket , Typ 0
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: TeXnicCenter.exe
P2: 2.0.1071 ...

There is still the UTF8 without BOM issue in TXC 2a2 (see http://www.latex-community.org/forum/vi ... 487#p26106).

Bug: After Windows resumes from hibernation, TXC 2a2 does sometimes not fully repaint its window (see screenshot).

The bug is not fully reproducible. The following steps trigger it sometimes:

1. Open TXC 2a2 with a project.
2. Let Windows go to standby.
3. Resume.
4. Repeat steps 2 and 3 some ...