Skip to content

[SPIKE] Investigate memory leak issues #184

@birschick-bq

Description

@birschick-bq

When I worked on another issue, the following tests have found memory leaks. They are disabled for now as root cause has not been identified.

BOOST_AUTO_TEST_CASE(TestFetchScrollLast*disabled()) {
  CheckFetchScrollUnsupportedOrientation(SQL_FETCH_LAST);
}
 
BOOST_AUTO_TEST_CASE(TestFetchScrollPrior*disabled()) {
  CheckFetchScrollUnsupportedOrientation(SQL_FETCH_PRIOR);
}
 
BOOST_AUTO_TEST_CASE(TestFetchScrollFirst*disabled()) {
  CheckFetchScrollUnsupportedOrientation(SQL_FETCH_FIRST);
}
BOOST_AUTO_TEST_CASE(TestOneRowObject*disabled()) {
...
}

BOOST_AUTO_TEST_CASE(TestCloseNonFullFetch, *disabled()) {
...
}

BOOST_AUTO_TEST_CASE(TestManyCursors, *disabled()) {
...
}

BOOST_AUTO_TEST_CASE(TestManyCursors2, *disabled()) {
...
}

Notes:

  • Using Dr Memory could find the memory leak but the call stack is empty. So I suspect this issue is only seen on Windows and it is a 3rd party library memory leak issue as nothing is found on Linux. Need check more to confirm.

  • No memory leak is reported on Linux after open detect_memory_leaks and enable TestFetchScrollLast - ./ignite-odbc-tests --catch_system_errors=false --detect_memory_leaks=1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions