You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting a memory error on the
getWorkBook function
so on line ~238
$streamData .= substr($rootdata, $pos, SMALL_BLOCK_SIZE);
I've already changed the max execution limit (0) and memory limit in my
.ini file is at 200M. I've also included the error reporting line for E_ALL
and E_NOTICE. For one, I installed AppServ on a Dell GX620 with 3.2Ghz P4
with 1 gig of ram on winxp. So, the AppServ and system aren't the greatest
but that's all I had to work with to access the local excel files. Next,
I'm looping through a readdir of about 2000 excel files (160M) in order to
extract a few bits of info from each. My script gets through about 1700 xls
files and extracts the info I need but it's not making it past the last
200-300. So, I'm really at a lost cause the scripts working great and I've
already changed the GetInt4d and _GetInt4d (magical??)functions but I'm on
32bit archy so results have been the same. I've also been unsetting
variables left and right.
I know there may be some problems due to the crap machine or AppServ quick
AMP install, but everything seems to be working and all the paths look good
to me.
Any suggestions on what I can try to get my script to finish to completion.
All I need is the data so the extended info cells is turned off (false) and
I hardcoded that in the function cause I think there were problems with the
call always being on, but I want to say the read() still wants to get
additional cell info which may be pushing the data chunks or memory limits.
Thanks for any ideas for me to try. Otherwise, very nice update to the
sourceforge and works in many other instances for me at 100% but this one
time I'm only getting about 90% completion.
Original issue reported on code.google.com by [email protected] on 9 Oct 2009 at 9:20
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 9 Oct 2009 at 9:20The text was updated successfully, but these errors were encountered: