messages/pmgrowl_json showing as page hits

is this the right behavior?

under admin/reports/hits,
almost for every "node" visit there is a "/messages/pmgrowl_json".

is there a way to filter this out or correct it so that it won't show up in reports?

Subscribe. There're lots of useless messages 'messages/pmgrowl_json' in users' trackers (navigation tab).

Hi,
I´ve had the same experience on my Sites.
You can kill this issue by simply putting exit(); after: drupal_json($data); in pmgrowl_json().
Doing so will prevent Drupal from counting this as a full PI.

What I noticed too, is that the polling of the jQuery Script for new Messages is acting like a PI and so the user is always Online if a Browser window is still open! You can reconstruct this easily using Author Pane and PM Growl on the same site. I´ve tried to kill this issue by faking something in _boot or _init but that doesn´t work and for sure isn´t realy good in performance. So what´s about looking for new messages via XML-RPC ??

I'm getting this in version 7.x too. putting exit(); after drupal_json($data); didn't kill this issue.

Do I have to open a new issue for version 7.x?

edit #1
I get a:

Location http:///messages/pmgrowl_json
Referrer http:///admin/modules
"Notice: Undefined variable: data in pmgrowl_json() (line 180 of /sites/all/modules/pmgrowl/pmgrowl.module)."

as well.

As far as I can see, I can't reproduce this locally, only in a live site.

How can I solve this?

edit #2:
This is another message I got in my live site:

Location: /messages/pmgrowl_json
Referrer: /messages/new
"PDOException: SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column 'uid' at row 1: INSERT INTO {pmgrowl_close} (mid, uid, closed) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2); Array ( [:db_insert_placeholder_0] => 124 [:db_insert_placeholder_1] => 33602 [:db_insert_placeholder_2] => 1 ) in drupal_write_record() (line 6868 in /includes/common.inc)."

Putting exit(); after drupal_json($data); (suggested in #4) didn't work for me too...

im still getting this for the drupal 7 version. has anyone fixed this?

Having same problem here with watchdog messages showing up in the user's tracker for Drupal 7.

I had a lot of message 403 "messages/pmgrowl_json" (users who lost cookies, unauthorized or etc, but still open browser)

helped add to pmgrowl.js:

if (!jQuery.cookie("DRUPAL_UID")) { return; }

after line "var pmGrowlCheckNew = function() {".

this for Drupal 7, when user unauthorized, script not send any request.

This issue appears on the d7 branch as well.

3 years and no fix :[

Is there a fix for this?