DateTime.Now in v4.0 Causes Dynamic Memory Allocations

kicks

comments: 0

DateTime.Now in v4.0 Causes Dynamic Memory Allocations (Unpublished)

DateTime.Now's new implementation in v4.0 is more memory-consuming than in previous releases. Even though the Int32 boxings issue was resolved, a new issue had emerged.

more less

Submit a new Story Link

You've got a new story for us? Awesome! Just fill in the details below and fire away...

DateTime.Now in v4.0 Causes Dynamic Memory Allocations

Edit your Story Link

Not quite right the first time? No problem, send us your changes...

Ban this user: Options

Please provide a reason for deleting this story

DateTime.Now in v4.0 Causes Dynamic Memory Allocations (Unpublished)