How about alloc(x*y||1)?

Hm. A global macro for image allocations then. Remember that you have image allocations in a lot of places. The allocation of the newly identified GL leak is done with xalloc(img->width*img->height);

But then again people use different allocators in different situations...

Currently xalloc throws an error on zero-allocations. The possibility for xalloc to throw errors is one reason why people not always want to use it, since often it is easier to write an if-statement than using ONERROR.