EXC_BAD_ACCESS drawInRect

[Igor-Palaguta]

Hello,

I've used in FICEntityImageDrawingBlock code from documentation:

UIGraphicsPushContext(context);
[image drawInRect:contextBounds];
UIGraphicsPopContext();

It worked excellent, but I could replicate EXC_BAD_ACCESS in drawInRect method. I reset image cache, but some pending operation was still in queue

Scenarios is following

threadX inside FICEntityImageDrawingBlock

UIGraphicsPushContext(context);
image = SomeImageTransformation

switch to main thread

[ imageCache reset ];

return back to threadX

[image drawInRect:contextBounds];
UIGraphicsPopContext();

[Igor-Palaguta]

As I can see from code FICImageTableEntry bytes (that were used during CGBitmapContextCreate initialization) are not available after reset, so any usage of this context finishes with EXC_BAD_ACCESS

[krisselden]

This bug makes testing very difficult.

[mallorypaine]

This behavior is expected. You shouldn't call reset while images are in use or being processed.

Why exactly are you doing that?

Sent from my iPhone

On Aug 4, 2014, at 5:57 PM, Kris Selden notifications@github.com wrote:

This bug makes testing very difficult.

—
Reply to this email directly or view it on GitHub.

[Igor-Palaguta]

During logout user from application, I want to reset everything

It can easily also be replicated with some code manipulation, after CGBitmapContextCreate call reset, and it reproduces easily

[mallorypaine]

I pushed a commit to master which may resolve this. Please let me know.

[krisselden]

I'm pretty sure that will work since it looks very similar to the workaround I use in the teardown of our tests.

[Igor-Palaguta]

Thank you guys, I am sure it should work