FYI when you run a "newer" release of Typo (somewhere in the late r800's) it consumes enough memory that the Textdrive servers will kill the process anyway. Until memory consumption can be reigned in, no one will be running a newer version of Typo on Textdrive's servers. Something holds on too way more memory than it should. I haven't been able to track it down yet.rake freeze_edge REVISION=3303
Mostly because other than ObjectSpace to see in general how many objects there are, I don't know of a way to see how much memory a given object/set of objects is taking up. Would a C extension to call sizeOf be necessary or the some other way to findout Object memory size in Ruby?
-Steve
On 3/28/06, Nicholas Van Weerdenburg <[EMAIL PROTECTED]> wrote:
Textdrive upgraded today already. No warning, broke my app.On 3/28/06, Gary Shewan <[EMAIL PROTECTED]> wrote:
On 28 Mar 2006, at 15:35, Jon Gretar Borgthorsson wrote:
> Well... Fixing the "enable_upload_progress" bug so that typo will work
> with rails 1.1 would be a start.
>
>
> -------------
> Jon Gretar Borgthorsson
>
> On 3/28/06, Scott Laird < [EMAIL PROTECTED]> wrote:
>> So, it's out. What do we do?
>>
Well apart from what Jon mentions, how far away is Typo from being
1.1 compatible? I do have a beady eye on it because last time
Dreamhost did the upgrade with no notice. I'd say the prospect of
hosting companies upgrading is still a few weeks away. There's time
there to look at what needs to be done.
Gary
_______________________________________________
Typo-list mailing list[email protected]
http://rubyforge.org/mailman/listinfo/typo-list
_______________________________________________
Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list
_______________________________________________ Typo-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/typo-list
