GoogleCodeExporter
commented
9 years ago I continue seeing this from time to time.Original comment by andreas....@gmail.com on 24 Jul 2013 at 7:16
Open GoogleCodeExporter opened 9 years ago
GoogleCodeExporter
commented
9 years ago I continue seeing this from time to time.Original comment by andreas....@gmail.com on 24 Jul 2013 at 7:16
GoogleCodeExporter
commented
9 years ago Do you still get this? It is basically the most common report I get from users.
Using v0.11-SNAPSHOT, as of today, one commit behind master. The application
log doesn't show anything unusal.Original comment by max.kell...@googlemail.com on 20 Jan 2014 at 8:18
GoogleCodeExporter
commented
9 years ago Any solution for this error?Me too getting same errorOriginal comment by abhishek...@gmail.com on 20 Jan 2014 at 8:34
GoogleCodeExporter
commented
9 years ago I still see this in user reports about twice a month.
Have you tried increasing your stack size?Original comment by andreas....@gmail.com on 20 Jan 2014 at 9:01
GoogleCodeExporter
commented
9 years ago Do you mean via android:largeHeap="true" or directly in the Thread constructor?
If this is some kind of infinite loop, would that really help?
Seeing that you don't get that so often, and that I run on a different coin
network, could this actually be bogus node behavior? If so I could try working
around it by breaking out of that loop if I detect this behavior.Original comment by max.kell...@googlemail.com on 20 Jan 2014 at 9:17
GoogleCodeExporter
commented
9 years ago Thought you might be using bitcoinj on a desktop. I'm not sure if
android:largeHeap increases stack size as well. When running own threads, you
can set the stack size, I've done this back in the time where wallets were
Java-serialized structures.Original comment by andreas....@gmail.com on 20 Jan 2014 at 10:00
GoogleCodeExporter
commented
9 years ago Should have mentioned that I'm running on Android and also a fork of your App
(which is great by the way). So what I got from this now, is that it's bogus
node behavior, as I'm seeing this a lot more often. That is, without tweaking
any of the networking/peering related code. My changes in the fork are
basically limited to network parameters and fee calculation.
Thanks for the help so far, if I find a "fix" for this, I'll let everyone know
:)Original comment by max.kell...@googlemail.com on 20 Jan 2014 at 10:51
GoogleCodeExporter
commented
9 years ago I need to rewrite the code to avoid recursion. For now we could just disable
this risk analysis as since the change to make timelocked transactions
non-standard has propagated everywhere the thing it's checking for is no longer
as important. I can put a temporary disable in for the 0.11 release.Original comment by hearn@google.com on 20 Jan 2014 at 7:53
GoogleCodeExporter
commented
9 years ago Any progress on this? Has the disable happened? I guess not, since this
exception is still regularly reported.Original comment by andreas....@gmail.com on 22 Mar 2014 at 4:54
GoogleCodeExporter
commented
9 years ago To add to my above comments:
I see this way less since my users stopped mining into the wallet. I think it
went down to once every two weeks I get a report like that. It was more like
once per day before.Original comment by max.kell...@googlemail.com on 22 Mar 2014 at 10:01
GoogleCodeExporter
commented
9 years ago The interesting part of these StackOverflowErrors is they tend to appear in
waves. Apparently there is network conditions with many chained pending
transactions. In these cases, I get like 10 of the same bug reports from
different people within one hour.
Anyway, a disable switch has been merged to master. I did not pick it for
0.11.2 because it felt a little bit too intrusive to me and the issue did not
itch enough.Original comment by andreas....@gmail.com on 27 Apr 2014 at 6:39
Original issue reported on code.google.com by
andreas....@gmail.comon 15 Apr 2013 at 9:06