oneVPL simple_encode memory

[Zanaboni__Gabriele]

Hi guys,

I have a problem running the simple_encode project from visual studio. The program itself works fine, in terms of output results.

The program read a raw file as input and encode it as h264 in output. The problem is related to the system memory that keep growing on during test.

For enphatize this behaviour i change the main call of simple_encode as this:

int main(int argc, char* argv[]) {
 
  int status = 0;
  for (int i = 0; i < 20; ++i)
  {
      std::ofstream output_stream("out.h264", std::ios::binary);
      status = EncodeFile("pathtoinputfile\\cars_1280x720.nv12", 1280, 720, output_stream);
      output_stream.flush();
  }

  return status;
}

Result the memory grows till the end of execution, only fall down at the end of program.

What's the matter with this?

Thanks

[Mark_L_Intel1]

Hi Gebriele,

Thanks for the good feedback and testing,

I want to reproduce this and could you give me more information?

• Which OS were you running the simple_encode?
• How do you monitor the increase of the memory?

Mark

[Zanaboni__Gabriele]

Hi Liu,

Sorry Sir,

Versione SO:                          10.0.18362 N/D build 18362
Produttore SO:                        Microsoft Corporation
Sistem Type:                          x64-based PC

I saw the increase of memory with Windows Resource Monitor.

Thanks

Gabriele

[Zanaboni__Gabriele]

Hi Liu,

I forgot the main option

Nome SO:              Microsoft Windows 10 Pro

Thanks

Gabriele

[Zanaboni__Gabriele]

Hi,

a new oneAPI release has come (beta07), but issue is still there.

Please, may someone tell me why memory keep on increasing till the end of for loop? Is it normal?

How can I fix this issue?

Thanks

Gabriele

[Luis_at_Intel]

Hi @Zanaboni__Gabriele 

Thanks for reporting this, and apologies for the delay in my response. As of now new Beta Update 8 is available for users to try and and I believe hello-encode sample too, if you have had a chance to try this using the latest available spec do you still observe this issue?

Regards,

Luis