Report returns results; but browser stuck on "Waiting for reports.xxx.com..."

(7 posts) (2 voices)

Tags:

No tags yet.

  1. ChrisFSB, Member

    I have a report that has worked well for years.

    Today - the report runs OK; and the browser displays it; but the browser tab hangs, and bottom left shows "Waiting for reports.xxx.com...". (Chrome and Edge)

    While it's "Hanging" the user cannot do anything with the report. Eventually the operation times out, and the user can interact with the report.

    Other reports, on the same server, run ok.

    Any ideas on how to debug this one report?

    Thanks, Chris
    --
    PHP 7.0.33
    myDBR 5.8.5 (build 4294)

  2. myDBR Team, Key Master

    You might want to check if this is a server side issue (try to wget the report content) or a client side (JavaScript?) issue. If you take the SQL export of the report and send it to support email, we can try to see if we can replicate the issue.

    --
    myDBR Team

  3. ChrisFSB, Member

    Thanks for the tip to use the wget - turned out the issue was client side.

    One of the columns defined as textin the db; needed to be selected with trim(textData). As soon as the trim was added; the problem went away.

  4. myDBR Team, Key Master

    Chris,
    could you check the difference between the following values from the same dataset:

    select sum(length(textData)) as 'Data', sum(length(trim(textData))) as 'Trimmed Data'

    --
    myDBR Team

  5. ChrisFSB, Member

    I think I've stumbled on the final solution:

    This data causes the report to hang:
    2727020049079608601120470632944400201216132710000000006A10EBC2B60A08420000000000000080907607023801000A2F850230001E000054601E00001E30D2800000000000

    If I use the MySQL QUOTE function then the output is quoted; and there is no hang:
    '2727020049079608601120470632944400201216132710000000006A10EBC2B60A08420000000000000080907607023801000A2F850230001E000054601E00001E30D2800000000000'

    QUOTE(a.rawData) as rawData,

  6. myDBR Team, Key Master

    Chris,
    looks like some browsers have trouble with regexp when encountering such a long text. This happens when myDBR is preparing data for sorting. You can do this:

    select 'dbr.sortmethod', 'colref', 'text';

    Where the 'colref' is a reference to the column. This will make myDBR skip determining the sorting based on the data (hence skipping the regexp) and it uses textual sorting.

    --
    myDBR Team

  7. ChrisFSB, Member

    Thanks for your help - perfect solution!

    Chris


Reply

You must log in to post.