[1271] Critical Errors

Have you captured any stacktraces of the failures?

No, but I will attempt to. However, getting the memory corruption ones will
be difficult as it kills VS as soon as it happens.

"Sergey Coox" <no_reply@jetbrains.com> wrote in message
news:3295470.149451247756035312.JavaMail.clearspace@app8.labs.intellij.net...

Have you captured any stacktraces of the failures?

>

---
Original message URL:
http://www.jetbrains.net/devnet/message/5241929#5241929

Also, I have been using 1272 for three hours now with no problems. This is
MUCH better than in 1271.

"Sergey Coox" <no_reply@jetbrains.com> wrote in message
news:3295470.149451247756035312.JavaMail.clearspace@app8.labs.intellij.net...

Have you captured any stacktraces of the failures?

>

---
Original message URL:
http://www.jetbrains.net/devnet/message/5241929#5241929

Here is one of the event log entries from the memory corruption crashes. I
do not know if it will help, but it is something.

Event Type: Error
Event Source: Microsoft Visual Studio
Event Category: None
Event ID: 5000
Date: 7/15/2009
Time: 4:21:52 PM
User: N/A
Computer: LS-BB-WS03
Description:
EventType clr20r3, P1 devenv.exe, P2 9.0.30729.1, P3 488f2b50, P4
system.windows.forms, P5 2.0.0.0, P6 4889dee7, P7 1521, P8 17, P9
system.invalidoperationexception, P10 NIL.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00 c.l.r.2.
0008: 30 00 72 00 33 00 2c 00 0.r.3.,.
0010: 20 00 64 00 65 00 76 00 .d.e.v.
0018: 65 00 6e 00 76 00 2e 00 e.n.v...
0020: 65 00 78 00 65 00 2c 00 e.x.e.,.
0028: 20 00 39 00 2e 00 30 00 .9...0.
0030: 2e 00 33 00 30 00 37 00 ..3.0.7.
0038: 32 00 39 00 2e 00 31 00 2.9...1.
0040: 2c 00 20 00 34 00 38 00 ,. .4.8.
0048: 38 00 66 00 32 00 62 00 8.f.2.b.
0050: 35 00 30 00 2c 00 20 00 5.0.,. .
0058: 73 00 79 00 73 00 74 00 s.y.s.t.
0060: 65 00 6d 00 2e 00 77 00 e.m...w.
0068: 69 00 6e 00 64 00 6f 00 i.n.d.o.
0070: 77 00 73 00 2e 00 66 00 w.s...f.
0078: 6f 00 72 00 6d 00 73 00 o.r.m.s.
0080: 2c 00 20 00 32 00 2e 00 ,. .2...
0088: 30 00 2e 00 30 00 2e 00 0...0...
0090: 30 00 2c 00 20 00 34 00 0.,. .4.
0098: 38 00 38 00 39 00 64 00 8.8.9.d.
00a0: 65 00 65 00 37 00 2c 00 e.e.7.,.
00a8: 20 00 31 00 35 00 32 00 .1.5.2.
00b0: 31 00 2c 00 20 00 31 00 1.,. .1.
00b8: 37 00 2c 00 20 00 73 00 7.,. .s.
00c0: 79 00 73 00 74 00 65 00 y.s.t.e.
00c8: 6d 00 2e 00 69 00 6e 00 m...i.n.
00d0: 76 00 61 00 6c 00 69 00 v.a.l.i.
00d8: 64 00 6f 00 70 00 65 00 d.o.p.e.
00e0: 72 00 61 00 74 00 69 00 r.a.t.i.
00e8: 6f 00 6e 00 65 00 78 00 o.n.e.x.
00f0: 63 00 65 00 70 00 74 00 c.e.p.t.
00f8: 69 00 6f 00 6e 00 20 00 i.o.n. .
0100: 4e 00 49 00 4c 00 0d 00 N.I.L...
0108: 0a 00 ..

"David Williams" <daviddwilliams@earthlink.net> wrote in message
news:h3nfgl$bap$1@is.intellij.net...

No, but I will attempt to. However, getting the memory corruption ones
will be difficult as it kills VS as soon as it happens.

>

"Sergey Coox" <no_reply@jetbrains.com> wrote in message
news:3295470.149451247756035312.JavaMail.clearspace@app8.labs.intellij.net...

>> Have you captured any stacktraces of the failures?
>>
>> ---
>> Original message URL:
>> http://www.jetbrains.net/devnet/message/5241929#5241929
>