EXC_BAD_ACCESS when calling Page_render

Hi,

we are copying the function updateImageForCellAtIndexPath of RDFileTableController from the sample code to my ViewController. The function running successfully inside the sample code. However when we tried to duplicate it to my own code, the EXC_BAD_ACCESS error occurred at the function call Page_render, attached please find the screen capture of the stack trace for function calls, could you please advise the possible reasons for the issue, or anything that we misconfigured?
We already followed the help to copy required libraries and environment settings, the project compiled successfully and got this runtime error. And we already enabled the Premium license.

It seems cannot upload image to this forum currently, below please find the stack trace we copied from xCode, thanks.

#0 0x0034ebd4 in CPDFStreamDCT::error_reporter(jpeg_common_struct*) ()
#1 0x002754a2 in jpeg_CreateDecompress ()
#2 0x00354770 in CPDFXRefTable::make_stream2(unsigned char*, int, char const*, CPDFDictionary const*) ()
#3 0x00351c2c in CPDFXRefTable::make_stream(CPDFStreamRec const*) ()
#4 0x0030ee46 in CPDFImage::load() ()
#5 0x002e91c0 in CPDFGRenderRGBA::show_image(CPDFImage*) ()
#6 0x002da290 in CPDFGProcessor::op_XObject(PDF_OPERATOR_ITEM const*, CPDFResources*, CPDFGRender*) ()
#7 0x002df520 in CPDFGProcessor::process(PDF_GPROCESS_PARA const*) ()
#8 0x00322812 in CPDFPage::render_page(CPDFGRender*, _RDMATRIX const&, int, CPDFPageSession&) ()
#9 0x002c44e2 in CPDFDoc::Page_Render(void*, CPDFGRender*, _RDMATRIX const&, int, CPDFPageSession&) ()
#10 0x00315a0a in Page_render ()

May you open a ticket in trouble ticket area, please?
Even if it seems an issue tight to your own code, enter it as bug submission then attach your own project.
We will check it.

Hi,

Ticket is opened, please help to follow, thanks.

Hi,

Have you found what the problem was? I'm having similar issue.

Thx.
Gregor

mostly, it happen when u are linking other jpeg library in project, i think (not sure).
link jpeg library cause conflict with our libraries.
so, you can wrap a shared library with our library to solve this issue.