|
|
See my previous message: "STB corruption on View test in ViewComposer..."
posted on 01/16/2001 for more information.
The problem has now damaged a view such that it can not be opened in the
ViewComposer. It seems to be a somewhat random problem. The class name,
in this case IdentityDictionary has become corrupt in the STB Collection. I
had been making changes in the ViewComposer and saved the view. Everything
worked the first few times. But then the last time I saved it the view
generated a walkback when I tried to show it that demonstrated this
corruption. When I tried to open it in the ViewComposer I got the same
walkback.
This is the beginning of the byte array. If you examine this as a string
you can see where the beginning of the IdentityDictionary class name has
been corrupted. I can send the entire byte array if it is needed.
#[33 83 84 66 32 48 32 78 8 12 0 10 0 0 0 83 84 66 86 105 101 119 80 114 111
120 121 0 0 0 0 78 2 13 0 1 0 0 0 83 84 66 67 108 97 115 115 80 114 111 120
121 0 0 0 0 54 0 6 0 83 116 114 105 110 103 7 0 0 0 68 111 108 112 104 105
110 146 0 0 0 10 0 0 0 68 105 97 108 111 103 86 105 101 119 38 0 5 0 65 114
114 97 121 27 0 0 0 0 0 0 0 0 0 0 0 194 0 0 0 2 0 0 0 1 0 144 1 1 0 2 0 96 0
0 0 0 0 0 0 6 3 3 0 82 71 66 0 0 0 0 129 1 0 0 129 1 0 0 129 1 0 0 0 0 0 0
135 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 14 2 26 0 83 84 66 73 100
101 110 116 105 116 121 68 105 99 116 105 111 110 97 114 121 80 114 111 120
121 0 0 0 0 122 0 0 0 0 0 0 0 160 0 0 0 146 0 0 0 18 0 0 0 180 106 162 8 116
105 116 121 68 105 99 116 105 111 110 97 114 121 194 0 0 0 32 0 0 0 90 0 0 0
0 0 0 0 122 0 0 0 0 0 0 0 160 0 0 0 146 0 0 0 13 0 0 0 67 111 110 116 97 105
110 101 114 86 105 101 119 194 0 0 0 15 0 0 0 0 0 0 0 96 0 0 0 194 0 0 0 2 0
0 0 54 0 12 0 76 97 114 103 101 73 110 116 101 103 101 114 4 0 0 0 0 0 1 68
65 0 2 0 96 1 0 0 0 0 0 0 242 0 0 0 0 0 0 0 129 1 0 0 129 1 0 0 129 1 0 0 0
0 0 0 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 7 12 0 66 111 114 100 101
114 76 97 121 111 117 116 0 0 0 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 26 1 0 0 0 0 0 0 48 1 0 0 194 0 0 0 16 0 0 0 90 0 0 0 0 0 0 0
122 0 0 0 0 0 0 0] asString
This looks like it could be a fairly serious problem. I am going to move to
another image incase something is bad in the image. However I would like
to try to understand this problem better. I would like to know what's
happening, and why.
Chris
|
Locked
