IT seems that 3.0.1 code has some big issues.
On Jun 21, 7:47 pm, b0b wrote:
> I noticed plenty of platform crashes on the A500.
> Here's what I got reported in various stack traces:
>
> java.lang.IncompatibleClassChangeError: interface not implemented
> at
> org.apache.harmony.xml.dom.No
On Tue, Jun 21, 2011 at 9:55 AM, b0b wrote:
> I also observed very weird crash reports in the platform itself (NPE,
> IncompatibleClassChangeError, failure to cast LinkedList to List)
> on the A500 running 3.0.1.
> So the question is if that version is completely broken ?
>
>
>
> On Jun 8, 5:52 p
I guess there are some bugs in 3.0.1 related to LinkedLists.
I don't think it's a A500 issue as I got ArrayStoreExceptions also on
a Samsung Galaxy Tab and an Asus Eee Pad Transformer, both running
3.0.1.
Since I replaced the LinkedList by a Vector no more crashes were
reported.
Cheers
Emanuel
O
I noticed plenty of platform crashes on the A500.
Here's what I got reported in various stack traces:
java.lang.IncompatibleClassChangeError: interface not implemented
at
org.apache.harmony.xml.dom.NodeListImpl.getLength(NodeListImpl.java:
51)
--
java.lang.ClassCastExcepti
I also observed very weird crash reports in the platform itself (NPE,
IncompatibleClassChangeError, failure to cast LinkedList to List)
on the A500 running 3.0.1.
So the question is if that version is completely broken ?
On Jun 8, 5:52 pm, Emanuel Moecklin <1gravity...@gmail.com> wrote:
> Just i
Just in case someone else runs into this problem.
It seems to be 3.0.1 related as I got more of those crash reports from
other 3.0.1 devices (none from 3.0 devices though): Acer Iconia & Asus
EeePad Transformer.
I changed my code to use a Vector instead so we'll see how that goes
(the only "solutio
Thanks for your analysis.
It's definitely a weird one. I got more strange crash reports from
Acer Iconia A500 3.0.1 devices which could indicate that either Acer
did some weird stuff or 3.0.1 is "special".
I'll keep an eye on it.
On May 27, 3:56 pm, Kostya Vasilyev wrote:
> This doesn't have to d
Can't debug it because it's a market crash report. I tried to
reproduce it but no "luck" so far.
Although I did try it on 3.0 and 3.1 only (where do I get 3.0.1
anyway?)
On May 27, 2:35 pm, Streets Of Boston wrote:
> Debug it.
> put getCell(i) into a variable and see what that variable is.
> And
This doesn't have to do with the types or null-ness of objects going into
the map, but rather with the implementaiton internals of LinkedHashSet.
LinkedHashMap . addNewEntry, line 193:
http://www.google.com/codesearch/p?hl=ru#cZwlSNS7aEw/libcore/luni/src/main/java/java/util/LinkedHashMap.java&q=L
Offhand it looks like some sort of system bug, but hard to tell where
-- Map source code, interface method resolution, heap management --
could be anywhere.
(But one thing to beware of is multithreading -- Only HashTable is
thread-safe, and HashMap/HashSet can be tied in a knot if modified
asynchr
Debug it.
put getCell(i) into a variable and see what that variable is.
And it seems that during run-time something is about to be stored in a
LinkedHash*Map* (and not in LinkedHashSet as shown in your code).
--
You received this message because you are subscribed to the Google
Groups "Android D
11 matches
Mail list logo
