ScopedFPDFPageObject page_object_deleter(page_object);On a similar note, should this line occur after the FPDFPage_RemoveObject call? And should it be changed to ASSERT_TRUE?
// Not calling release() since ownership will be returned below in theIs this a little more dangerous? Could there be a double free possible on test failure?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
On a similar note, should this line occur after the FPDFPage_RemoveObject call? And should it be changed to ASSERT_TRUE?
The only ways for FPDFPage_RemoveObject() to fail here are:
1) `page` is invalid, but that shouldn't happen and the test would probably have failed or crashed before getting here.
2) `page_object` is null. In which case, there's no chance of a double free.
// Not calling release() since ownership will be returned below in theIs this a little more dangerous? Could there be a double free possible on test failure?
There's no ASSERT_FOO() call between here and line 2243, but I can release() here.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
ScopedFPDFPageObject page_object_deleter(page_object);Lei ZhangOn a similar note, should this line occur after the FPDFPage_RemoveObject call? And should it be changed to ASSERT_TRUE?
The only ways for FPDFPage_RemoveObject() to fail here are:
1) `page` is invalid, but that shouldn't happen and the test would probably have failed or crashed before getting here.
2) `page_object` is null. In which case, there's no chance of a double free.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Remove FPDFPageObj_Destroy() calls in fpdf_edit_embeddertest.cpp
Use ScopedFPDFPageObject instead.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |