~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@eyedeekay
@orignal
@postman
@zzz
%Liorar
%ardu
%cumlord
%snex
+FreefallHeavens
+Xeha
+bak83
+hk
+poriori
+profetikla
+qend-irc2p
+r00tobo
+uop23ip
+weko
AHOH
Arch
BubbRubb1
Danny
DeltaOreo
FreeRider
HowardPlayzOfAdmin
Irc2PGuest73758
Meow
Onn4l7h
Onn4|7h
T3s|4__
acetone_
boonst
evasiveStillness
l337
mareki2p_
not_bob_afk
not_human
pisslord
r00tobo[2]
shiver_
simprelay
solidx66
u5657
usr001
zer0bitz
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.