[ 
https://issues.apache.org/jira/browse/KARAF-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16375932#comment-16375932
 ] 

ASF subversion and git services commented on KARAF-5632:
--------------------------------------------------------

Commit 7564871b78ec59012800b08d447bd961d201e205 in karaf's branch 
refs/heads/karaf-3.0.x from [~rhierlmeier]
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=7564871 ]

[KARAF-5632] Reuse in HeapDumpProvider now the copy function of LogDumpProvider 
to copy the dump file.


> dev:create-dump creates invalid dump file
> -----------------------------------------
>
>                 Key: KARAF-5632
>                 URL: https://issues.apache.org/jira/browse/KARAF-5632
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 3.0.8
>         Environment: karaf 3.0.8, windows 10
>            Reporter: Richard Hierlmeier
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 3.0.9
>
>         Attachments: screenshot-1.png
>
>
> When creating with the {{dev:create-dump}} command an heap dump, this dump 
> can not be opened with eclipse memory analyser I  get the following error:
> {noformat}
> The HPROF parser encountered a violation of the HPROF specification that it 
> could not safely handle. This could be due to file truncation or a bug in the 
> JVM. Please consider filing a bug at eclipse.org. To continue parsing the 
> dump anyway, you can use -DhprofStrictnessWarning=true or set the strictness 
> mode under Preferences > HPROF Parser > Parser Strictness. See the inner 
> exception for details.
> The HPROF parser encountered a violation of the HPROF specification that it 
> could not safely handle. This could be due to file truncation or a bug in the 
> JVM. Please consider filing a bug at eclipse.org. To continue parsing the 
> dump anyway, you can use -DhprofStrictnessWarning=true or set the strictness 
> mode under Preferences > HPROF Parser > Parser Strictness. See the inner 
> exception for details.
> (Possibly) Invalid HPROF file: Expected to read another 83.886.080 bytes, but 
> only 1.500 bytes are available.
> (Possibly) Invalid HPROF file: Expected to read another 83.886.080 bytes, but 
> only 1.500 bytes are available.
> {noformat}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to