In a multisector flight you book a group of 6 to the first stop, you must remember to free all the group’s seats rather than the seat occupied by the group leader. If you only mark the seat of the group leader as empty then you have 5 adjacent seats that are free but the booking system sees as being occupied. Repeat this a couple of times the booking system will see the flight as being full when it is not. The memory that is unoccupied but still marked as full on the booking system is said to have leaked away.
This is only an issue with one programming language, however this is most prestigious language and proper memory management is seen as a mark of a good programmer. Since XP has as many as 2^32 seats the odd drip here and there isn’t a problem but well written apps shouldn’t leak.
I'm sure this hasn't helped
