in reply to Re: Hard to Debug windows memory error
in thread Hard to Debug windows memory error

Hi. I've briefly reviewed this entire thread, but I did not expand every readme, nor follow every link;

Did you ever post (minimal) code that demonstrates this issue?

I ask, because vaguely remember reading your OP from 5 months ago and thinking that when you got around to posting code that I could run, that demonstrated the problem, this would probably be quite simple to tie down to a cause. From my review, you never have?

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)
In the absence of evidence, opinion is indistinguishable from prejudice.
  • Comment on Re^2: Hard to Debug windows memory error

Replies are listed 'Best First'.
Re^3: Hard to Debug windows memory error
by jandrew (Chaplain) on May 11, 2016 at 20:14 UTC
    BrowserUk++ Thank you for offering. The original intent of my first post was indeed to look for techniques I could use to simplify the case. I did follow several suggestions provided by other monks but I remain unsuccessful. I kept working on the problem for awhile but eventually was only able to infer an issue not demonstrate it. From a practical standpoint the solution implemented in the new package doesn't fail so I feel somewhat vindicated in my inference but at best it remains just that - a guess. The obsessive compulsive person in me hates that I just walked away from the simplification task but I feel like I tried all avenues.

    If you want to review the complex case here is a link to the Travis-CI failing output https://travis-ci.org/jandrew/Spreadsheet-XLSX-Reader-LibXML/jobs/129510108 and here is a link to the package code that fails https://github.com/jandrew/Spreadsheet-XLSX-Reader-LibXML or I have also posted to CPAN with a deprecation warning https://metacpan.org/pod/Spreadsheet::XLSX::Reader::LibXML.

[reply]

      Okay. I see that it is a complex problem that you've at least worked your way past if not actually fixed.

      (Did you check the Application Event logs on the failing machines?)

      With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

        I did check the application event logs as well as running several windows style c debuggers but none of the things I found and worked on with my skill set seemed to impact the core problem. (re-installing another version of Visual Studio, adding to Path so .dlls would be recognized etc.) I still don't have a solid understanding of where the root of the problem even lies. In truth I have never had a fail like this with perl before. I deeply respect XML::LibXML too so the fact that they don't play well together in this case was painful.

[reply]

In Section Seekers of Perl Wisdom