People
Repo info
Activity
  • Jan 13 22:17
    daehlerr closed #785
  • Jan 13 22:17
    daehlerr commented #785
  • Jan 13 22:03
    daehlerr commented #785
  • Jan 13 21:19
    thomassross commented #783
  • Jan 13 21:19
    thomassross commented #783
  • Jan 13 21:18
    SamCarlberg commented #783
  • Jan 13 20:48
    SamCarlberg commented #785
  • Jan 13 20:47
    SamCarlberg reopened #785
  • Jan 13 20:47
    SamCarlberg closed #785
  • Jan 13 19:01
    daehlerr opened #785
  • Jan 13 18:15
    CoffeeMusicCode starred WPIRoboticsProjects/GRIP
  • Jan 13 18:05
    KidQuid starred WPIRoboticsProjects/GRIP
  • Jan 13 10:03
  • Jan 13 05:35
    Tigris-Cinis starred WPIRoboticsProjects/GRIP
  • Jan 12 23:29
    Travis SamCarlberg/GRIP (better-logging) still failing (429)
  • Jan 12 21:13
    thomassross commented #783
  • Jan 12 02:21
    nightpool commented #782
  • Jan 12 02:18
    nollchr commented #784
  • Jan 12 02:17
    SamCarlberg commented #784
  • Jan 12 02:09
    nollchr commented #784
Austin Bennett
@ZeusChops
Okay, so it at least narrows it to something funny with arch then.
Austin Bennett
@ZeusChops
I'm having troubles creating an Arch linux vm to test GRIP on to verify if its an arch linux-specific thing. Can you post the log file(s) from GRIP somewhere? (pastebin, or github gist ) @johnyburd
that's the result of ./gradlew :ui:run --debug > log.txt
Sam Carlberg
@SamCarlberg
--debug is for debugging Gradle, it's not something of ours
Jonathan Buchanan
@johnyburd
oh whoops
you probably don't want to look through all 5000 lines of that
Sam Carlberg
@SamCarlberg
Not really
Jonathan Buchanan
@johnyburd
so that without debug is what you want though?
Sam Carlberg
@SamCarlberg
It probably won't be useful
Are you familiar with the VisualVM app?
Jonathan Buchanan
@johnyburd
no
Sam Carlberg
@SamCarlberg
It's a useful tool for profiling memory and CPU use for Java programs. You can download it here
Jonathan Buchanan
@johnyburd
I just installed it. I'm not sure where to get the file I need to analyze though
Sam Carlberg
@SamCarlberg
If you run GRIP, it'll show up in the left-hand pane. Probably as "local application" if you're launching the native app
Jonathan Buchanan
@johnyburd
okay I got grip.ui.main and graddlewrapper
Sam Carlberg
@SamCarlberg
double-click the grip.ui.main one
then open the "monitor" tab
Jonathan Buchanan
@johnyburd
okay
Sam Carlberg
@SamCarlberg
Now add the webcam source and see if the heap use or size increase
Jonathan Buchanan
@johnyburd
the size is increasing but not the use
Sam Carlberg
@SamCarlberg
What's the total size of the heap? And what's the total memory use according to your system?
Jonathan Buchanan
@johnyburd
the heap size was ~1 GB
my system said closer to 6 GB
I had to close it before it crashed
Sam Carlberg
@SamCarlberg
What JDK do you have installed?
Jonathan Buchanan
@johnyburd
the metaspace never got bigger btw
Sam Carlberg
@SamCarlberg
Metaspace almost never increases, that's for stuff like classes that get loaded
Jonathan Buchanan
@johnyburd
jre8-openjdk 8.u112-1
Sam Carlberg
@SamCarlberg
Okay. This is because the OpenCV native objects aren't getting freed up soon enough. We've set up GRIP to periodically prompt the JVM to run garbage collection, but it's not always guaranteed to run. Your version of the JVM doesn't seem to want to run GC often enough
And you still have this problem with the native GRIP app we distribute?
Jonathan Buchanan
@johnyburd
uh, the only thing I've used is whatever is on github
Sam Carlberg
@SamCarlberg
The .deb file from here
Jonathan Buchanan
@johnyburd
uhh arch doesn't normally use dpkg
though I suppose I could try that
Sam Carlberg
@SamCarlberg
If you're just running GRIP from Gradle, you can also limit the heap size with ./gradlew :ui:run -PjvmArgs=['-Xmx200M']
Jonathan Buchanan
@johnyburd
hmm. my gradle doesn't recognize that as an option
Sam Carlberg
@SamCarlberg
Sorry, it should be ./gradlew :ui:run -PjvmArgs="-Xmx200M"
Though that still won't fix the GC problem, it will help the memory usage. You could also add -Xmaxsize=16m in the jvmArgs string
Jonathan Buchanan
@johnyburd
the second one caused it to fail
Sam Carlberg
@SamCarlberg
Whoops. -XX:MaxNewSize=16M
JVM arguments are weird
Jonathan Buchanan
@johnyburd
haha yeah
Jonathan Buchanan
@johnyburd
well
that didn't fix it
the heap size is staying constant but my system memory still rises
Sam Carlberg
@SamCarlberg
Still crashing?
Jonathan Buchanan
@johnyburd
I didn't leave it that long but it was still collecting
it's rather a pain to let it crash because it freezes my whole system