Leaks with NSDate

[wsnnn]

Faced with such a problem: with each operation with a base leak. Xcode Instruments indicates iActiveRecord [NSDate dateWithTimeIntervalSince1970:] and [NSDate dateWithTimeIntervalSinceNow:]

//on the Russian Столкнулся с такой проблемой: при каждой операции с базой происходят утечки. Xcode Instruments указывает на iActiveRecord [NSDate dateWithTimeIntervalSince1970:] и [NSDate dateWithTimeIntervalSinceNow:]

[AlexDenisov]

Hi @wsnnn, could you describe steps to reproduce?

[AlexDenisov]

And which version do you use?

[wsnnn]

Hi! Download stable version 29.06.2013.

Here is the sample project. Tested on the iPad. The results are the same as above. http://yadi.sk/d/a4NYU6gV6P4-4

[AlexDenisov]

Thank you, I'll review it soon.

[AlexDenisov]

Could you try the new version from master branch? stable branch have a lot of bugs, and now I've implemented AR with the new API

Here is #35 some discussion, also you may review ActiveTwitter target.

P.S. or you can drop me on skype: debian.1101

[wsnnn]

Tried master. The same. Added class_getSubclasses

[AlexDenisov]

Fixed on stable branch. But I cannot reproduce this on master...

[wsnnn]

By the way, ActiveTwitter uses old API http://search.twitter.com/search.json?q=test

[AlexDenisov]

f**k, I will fix it.

[wsnnn]

Maybe this will help http://yadi.sk/d/4C4WG0Qk6PIuM

[wsnnn]

stable ARTest(68825,0x3d1a0b88) malloc: *** error for object 0x1f5d4890: pointer being freed was not allocated. *** set a breakpoint in malloc_error_break to debug

[AlexDenisov]

I will review this at the evening. Anyway, I highly recommend to use version from master.

[wsnnn]

While I use master. Since AR is used in the life cycle very often, the leaks are very large.

[AlexDenisov]

I can't understand where is the problem. I had the same trace for stable, but master' trace looks good, without leaks.

[wsnnn]

Master shows on each call to the database: malloc: *** error for object 0x1f5d4890: pointer being freed was not allocated.

[AlexDenisov]

Have you called [ActiveRecord applyConfiguration... at the app start?

[wsnnn]

No

[AlexDenisov]

Could you try and leave a feedback?

[wsnnn]

Posted on your mail

[holin]

Any thing new? I have this issue too.

[alexiscreuzot]

+1

[alexgaribay]

Update please?

[AlexDenisov]

Guys, could someone give me a test project with these leaks?

[alexgaribay]

@AlexDenisov I sent you an email with a failing project presuming the email listed in the wiki is yours.

[AlexDenisov]

@alexgaribay, I've received your email and will review it soon, thanks.

[ghost]

Any updates on this? I am trying to set a property of type NSDate to something, then update the entity, but it saves null. @AlexDenisov

[alexiscreuzot]

I think it wouldn't be a bad idea to save dates as timestamps (NSNumber) for now, at least until the problem is resolved.

[ghost]

@kirualex Yeah you could even save them as ISO8601 strings but that isn't solving the problem, I don't like spikes sitting somewhere in my app. Plus to that, changing even a small property like that results in a lot of refactor.

[AlexDenisov]

I still can't reproduce it nor on master branch, nor on stable.

[AlexDenisov]

@nemesis-fw, regarding your issue with null date: have you marked the property as @dynamic?