Posted By

ajbatac on 11/04/10


Tagged

bug Friendfeed ffbackup


Versions (?)

ffbackup bug?


 / Published in: Java
 

  1. Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
  2. at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
  3. at java.lang.Class.getConstructor0(Unknown Source)
  4. at java.lang.Class.getDeclaredConstructor(Unknown Source)
  5. at com.sun.xml.internal.bind.v2.ClassFactory.create0(Unknown Source)
  6. at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.createInstance
  7. (Unknown Source)
  8. at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallingContex
  9. t.createInstance(Unknown Source)
  10. at com.sun.xml.internal.bind.v2.runtime.unmarshaller.StructureLoader.sta
  11. rtElement(Unknown Source)
  12. at com.sun.xml.internal.bind.v2.runtime.unmarshaller.ProxyLoader.startEl
  13. ement(Unknown Source)
  14. at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallingContex
  15. t._startElement(Unknown Source)
  16. at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallingContex
  17. t.startElement(Unknown Source)
  18. at com.sun.xml.internal.bind.v2.runtime.unmarshaller.SAXConnector.startE
  19. lement(Unknown Source)
  20. at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startEle
  21. ment(Unknown Source)
  22. at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scan
  23. StartElement(Unknown Source)
  24. at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
  25. l$FragmentContentDriver.next(Unknown Source)
  26. at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(U
  27. nknown Source)
  28. at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next
  29. (Unknown Source)
  30. at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
  31. l.scanDocument(Unknown Source)
  32. at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(U
  33. nknown Source)
  34. at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(U
  35. nknown Source)
  36. at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown So
  37. urce)
  38. at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Un
  39. known Source)
  40. at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.p
  41. arse(Unknown Source)
  42. at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.un
  43. marshal0(Unknown Source)
  44. at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.un
  45. marshal(Unknown Source)
  46. at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(Unknown Sou
  47. rce)
  48. at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(Unknown Sou
  49. rce)
  50. at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(Unknown Sou
  51. rce)
  52. at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(Unknown Sou
  53. rce)
  54. at org.patrickestarian.ff.Backup.loadXML(Backup.java:125)
  55. at org.patrickestarian.ff.Backup.loadFeedsFromFF(Backup.java:81)
  56. at org.patrickestarian.ff.Backup.<init>(Backup.java:58)
  57. at org.patrickestarian.ff.Backup.main(Backup.java:306)

Report this snippet  

Comments

RSS Icon Subscribe to comments
Posted By: patrickestarian on November 4, 2010

Thanks for reporting it.

Two questions:

1- Approximately, how much free memory you had when you were running the program? (if you just tell me that you had more than 500 MB, that's enough for me)

2- Could you replicate the problem? if yes, which file does it die on?

Thanks again

Posted By: ajbatac on November 7, 2010

1) I have more than 30GB of free space and running a machine with 4GB of RAM 2) I was here when it stopped. http://friendfeed.com/ajbatac/89c49387/server-speed-tests don't know if that's the reason. So honestly I don't know how to answer your question.

Question: If I run it again, using the same parameters. Would it: a) Start where it ended? b) Overwrite the current XML files c) Create duplicates?

Thanks again, Patrick. Great job.

You need to login to post a comment.