Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libtizonia: scheduler never destroys the object system #35

juanrubio opened this issue Apr 2, 2014 · 0 comments


None yet
1 participant
Copy link

commented Apr 2, 2014

  • tizscheduler.c:deinit_servants needs to call tiz_os_destroy
  • This is the memory leak location as reported by Valgrind
   (1) ==9712== 182,648 (528 direct, 182,120 indirect) bytes in 11 blocks are definitely lost in loss record 266 of 266
   (1) ==9712==    at 0x4C2C510: calloc (in /usr/lib/valgrind/
   (1) ==9712==    by 0x6287015: tiz_mem_calloc (tizosalmem.c:69)
   (1) ==9712==    by 0x628F8BF: map_calloc (tizosalmap.c:97)
   (1) ==9712==    by 0x628F978: tiz_map_init (tizosalmap.c:116)
   (1) ==9712==    by 0xDC35BB3: tiz_os_init (tizobjsys.c:470)
   (1) ==9712==    by 0xDC33F75: init_servants (tizscheduler.c:2118)
   (1) ==9712==    by 0xDC2F00B: do_init (tizscheduler.c:621)
   (1) ==9712==    by 0xDC330CE: dispatch_msg (tizscheduler.c:1885)
   (1) ==9712==    by 0xDC33591: il_sched_thread_func (tizscheduler.c:1972)
   (1) ==9712==    by 0x74D5181: start_thread (pthread_create.c:312)
   (1) ==9712==    by 0x720230C: clone (clone.S:111)

@juanrubio juanrubio added this to the OpenMAX IL 0.1.0 milestone Apr 2, 2014

@juanrubio juanrubio added the bug label Apr 2, 2014

@juanrubio juanrubio self-assigned this Apr 2, 2014

@juanrubio juanrubio closed this in 88363ec Apr 2, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.