Ticket #1114 (new defect)

Opened 5 years ago

Last modified 5 years ago

Wrong error handling in osync_try_malloc0

Reported by: bricks Owned by: dgollub
Priority: normal Milestone:
Component: OpenSync Version: 0.38
Severity: minor Keywords:


osync_try_malloc0 calls osync_error_set if no more memory could be allocated. osync_error_set internally uses g_malloc0. Therefore osync_try_malloc0 tries to request additional memory in case of empty memory. Beyond that g_malloc0 calls abort() if the memory is empty. This results always in a termination of opensync if osync_try_malloc0 is used and no memory could be allocated.

Change History

comment:1 Changed 5 years ago by dgollub

Sounds sane to me...

Any idea how to handle this?

Note: See TracTickets for help on using tickets.