~dr|z3d
@RN
@StormyCloud
@T3s|4_
@orignal
@postman
@zzz
%acetone
%mareki2p
%snex
+FreefallHeavens
+Onn4l7h
+Onn4|7h
+Over
+fa
+marek22k
+onon_
+poriori
+profetikla
+qend-irc2p
+r00tobo
+sexy
+uberius
+uop23ip
Arch
Atticfire
Danny
Irc2PGuest21708
Irc2PGuest28384
Irc2PGuest66257
Irc2PGuest75631
Irc2PGuest99986
RTP_
T3s|4
U1F642
Watson
ahiru
anontor
cims
i2potus
interesting
lokzz
luvme3
mahlay
makoto
n2_
nilbog
not_bob_afk
pinotto
r00tobo[2]
rednode
user_ygg2_
dr|z3d
does this look saner, or am I making the same mistake here?
dr|z3d
b32 = reader.readLine();
dr|z3d
if (b32 == null) {return;}
zzz
same
dr|z3d
yeah, figured.
dr|z3d
so, totally pointless then, as you say. this should cover it: while((b32 = reader.readLine()) != null) {
dr|z3d
well, not totally pointless, as it prevents the issue from triggering, but not the correct fix.
dr|z3d
what about checking the filesize instead?
dr|z3d
int fileLength = (int) file.length();
dr|z3d
if (fileLength == 0) {return;}
zzz
better
zzz
but the reason for a ticket was that this is low priority, not for today, so if you want my analysis you'll have to sit tight ))
dr|z3d
sure, I don't think it's something that'll affect most people.
dr|z3d
if there's no file at all, non-issue. only zero length file, or presumably a file containing no b32s.
dr|z3d
got a stacktrace zzz, bug report updated.