[cups.development] notifier - Get-Job-Attributes client-error-bad-request

[Michael Sweet]

On Apr 22, 2010, at 4:02 PM, Rodger Devine wrote:
> ...
> I'm using ps to monitor the virtual memory size of the notifier in bytes.

VSIZE isn't a great measurement number since it isn't just malloc use...

> A) running before new job-state-changed event occurs:
> 
> lp        8314  0.0  0.2   6712  2448 ?        S    Apr21   0:00 
> /usr/lib/cups/notifier/jnotify jnotify
> 
> B) after previous subscription event occurs:
> 
> lp        8314  0.0  0.2   6724  2460 ?        S    Apr21   0:00 
> /usr/lib/cups/notifier/jnotify jnotify 
> 
> And so forth. It grew to over 20 kb after running for over a day.
> 
> However, when I remove the following lines of code after the 
> cupdsDoRequest call, this increase in memory usage does *not* occur, 
> which has led me to believe there's some type of leak:
> 
>       if (response->request.status.status_code > IPP_OK_CONFLICT)
>       {
>          fprintf(stderr, "jnotify: %s\n", cupsLastErrorString());
>          ippDelete(response);
>          return (0);
>       }
> 
> I can email you the entire source directly (~465 lines) if my code 
> snippets aren't clear.

Maybe that would be the best place to start.

________________________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair