comment on

I'd suggest waiting until 1st October before submitting the bug report. That'll give about a week (from the time of the original post) for any further feedback: PM tends to be quieter over the weekend, so there may be more to come.

In your bug report, I'd stick to what you know: problem on these (list) Perl & Tk combinations; but no problem on these (other list) combinations. I would avoid conjecture altogether: "I'm pretty sure ..."; "I would expect ..."; and similar. It's likely that maintainers have their own testing environments: they can confirm what you report as well as testing other scenarios.

I'd also include a link to this thread: your report can summarise findings; with the link back to here for details. It shows that you made an effort before raising the bug report. There may be additional information by the time someone gets around to looking at the problem.

— Ken

In reply to Re^3: Perl Tk crashes when mem usage exceeds 4G on Win10 by kcott
in thread Perl Tk crashes when mem usage exceeds 4G on Win10 by boleary

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


laziness, impatience, and hubris
	PerlMonks