We programmers are a lazy bunch; we only work on a problem until a "good enough" solution is achieved. I suppose crashing and blaming it on android is good enough in this circumstance.
I've got my own "good enough" solution, which involves bypassing creating all those java strings in the first place, and compressing the raw ascii using a nifty compression utility called "smaz" that I found on github. This is a much better solution than the simple solution that didn't work, and I never would have got there if the simple solution worked. So thanks. On Monday, September 28, 2020 at 7:42:12 PM UTC-7 Shai Almog wrote: > You can look at the code of GZIPOutputStream in Codename One. It's all > pure Java and as far as.I can tell doesn't do that. > We didn't write it though. > > Again, this is Androids subsystem. Not us. So your beef is with Google. > We don't garbage collect on Android. We don't throw exceptions. This is > 100% Google. > > On Monday, September 28, 2020 at 8:50:37 PM UTC+3 [email protected] > wrote: > >> >> I more or less agree, but 1000x worse performance suggests either that >> something sloppier >> than normal is going on, such as perhaps writing an explicit file in >> GzipOutputStream. >> >> Also, if the app just crashes instead of (presumably) throwing an out of >> memory exception, >> that's on you. I call to your attention once again the issues I've filed >> about the garbage >> collector crashing in circumstances like this. >> >> -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/40f0950d-082e-4698-86b7-8d5634a8621cn%40googlegroups.com.
