I'm encountering a problem while using 2 Matrox Extio F2408 devices.
I run a Centos 5.0 system with 5 monitors, 4 connected to the first Extion device, the fifth to the second.
Xinerama mode is enabled.
All is fine but when we open an application feature using OpenGL (implemented in Java with JOGL) the CPU
jumps in 100% and the memory consumption of our application increases dramatically. The application freezes like this.
I have this problem only when we connect both Extio devices in Xinerama mode. With only one device in Xinerama,
or with both of them but without Xinerama there is no problem.
I have updated to the latest official matrox video card driver but this was not a solution.
Could you point me in the right direction in debugging or solving this problem?
Related
Now you can easily notice I am new on app development path when I am setting up Android studio for Android development I find that my pc need specific requirements (Hardware) to start
But I have desktop that
CPU : Core 2Duo
RAM : 4 GB
HDD : 500 GB
It's been week when I just run some basic apps but it's very headache to do it for basics app because my android studio every minute got hang and start lagging I can't open chrome there full of warehouse of my problems related to pc because of android studio
Anyone know any hacks or by tips for me you can feel free for it.
Putting it bluntly: those specs are simply not enough to do any serious modern development. If you could replacing the HDD with an SSD (even a small, cheap one) would be the highest priority and more memory is second. A better CPU would obviously help, but it's a luxury, the other two items are more important.
Assuming that's not an option, you can do either of those two things:
don't use an IDE (or at least a more light-weight one, such as VS Code) and build your software from the command line. This will be more painful (especially when you're just starting) and even then the resource requirements of the build will be non-trivial.
Make sure to do as little as possible on your local machine. If you have a decent internet connection, then you might be better off developing on a free remote cloud computer and use something like Projector to show the UI in the browser. I've found this repo with instructions on how to use it with Android Studio, which seems useful, but I've not verified that it works.
The only hacks I can think of are:
Make sure you are not using a remote mounted file system or "share" for either your Android Studio + Java installation or your AS workspace.
Shutoff (quit) all other applications that are using significant amounts of RAM; e.g. your web browsers, your email tool, Slack, Zoom, etc.
If you are using Windows, switch to Linux.
Better idea: get a better development machine. I think that the RAM is most important, because it sounds like your machine is thrashing.
It may seem unfair but Android Studio is not really suitable to run in a lower end device. It used to lag/hang in my device with Core i7 and 8GB Ram. The best thing you can do is to use an SSD instead of HDD. SSDs with smaller memory are often cheap and this alone can somewhat lessen your problems with Android Studio.
i think you should change your HDD to 240 GB SSD and it will works fine
I'm currently using a Samsung Galaxy A20s with a total of 2790MB ram.
the phone was originally developed for Android 9.0 Pie and it has been getting upgrades and I'm currently on Android 11 Honeycomb which is a good thing but the hardware on the phone can't keep up. my ram is always almost full and according to Droid Info app my Java Heap size is 192MB !!!. that's way too much!!
is there any way to reduce the heap size on my smartphone?
One way is you can root your smartphone and get almost full access for example remove factory installed apps, overclock your CPU, increase RAM etc. But rooting will void the warranty and also if your smartphone is uncommon, do it at your own risk !
Read more about it here
https://www.xda-developers.com/root/
I am currently working on an image processing project using Java OpenIMAJ library. I need to grab frames from multiple cameras (using Logitech C270 USB Webcams right now) to perform manipulations on the grabbed frames.
I have hit a snag right now. I am able to add 2 cameras when both are running at 640X480 resolution and 3 cameras when the resolution is reduced to 320X240 for all three.
But I need to read the outputs from at least 5 cameras at reasonably good resolution to correctly perform my operations. Is this a limitation on the part of the hardware I am using or a software limitation?.. I have listed some details that I believe could help. Do let me know if you need any further information.
Windows 7 Professional 64bit
JDK 1.7
OpenIMAJ v1.1
Pentium Dual-Core E5700 # 3.00GHz
4GB RAM
No dedicated Graphics
Webcams are connected to USB 2.0 ports
(Windows Experience Index 4.1)
Exception thrown for 3rd camera at 640x480 resolution is
org.openimaj.video.capture.VideoCaptureException: An error occured opening the capture device
Any comments on why I am getting this limitation would be very helpful.
Thanks in advance
In all likelihood this is down to a hardware limitation; streaming from multiple cameras tends to saturate the USB bus. We managed 6 cameras on two separate busses at 320x240 resolution on a single laptop before: http://blog.soton.ac.uk/multimedia/2011/08/01/goggles/
I'm using the ADT bundled virtual device manager to test my application (using the Intel image and have installed HAXM as well), but the emulator is very sluggish.
My system's base config is:
Core i7 920 (overclocked) / GTX 590 / 8GB ram / Win7.64
I've allocated 512 MB of ram to the virtual device. I've also tried with 1GB and 2GB allocations, but they made no difference whatsoever - the sluggishness remained.
For various reasons, I cannot use other emulators along with virtual box. Is there a way I can get this default emulator to run smoothly like it would on a well powered smartphone, ensuring a constant draw rate of 60 fps or higher?
(On a side note: Is this a hardware limitation, and would upgrading to a very high end development machine, say one with a top-end Xeons, 16+ GB ram and SSD Raid configurations improve things?)
The Android Emulator is currently very slow.
However, if it's not already done you may enable the GPU.
If you are running the emulator from Eclipse, run your Android application using an AVD with the -gpu on option enabled:
In Eclipse, click your Android project folder and then select Run > Run Configurations...
In the left panel of the Run Configurations dialog, select your Android project run configuration or create a new configuration.
Click the Target tab.
Select the AVD you created in the previous procedure.
In the Additional Emulator Command Line Options field, enter:
-gpu on
Run your Android project using this run configuration.
Source
Maybe your video driver is out of date. Make sure you use the latest video driver.
My emulator's performance improved after updating the video driver (and I'm using an Intel HD 4000 graphic card).
if I wanna work/test with my AVD, the Android emulator is super slow, barely usable. Im developing with eclipse and was just about testing a helloWorld app., but the whole thing runs too slow. Is it the hardware of my pc?
details:
AMD Athlon 64 3500+, 2.21 Ghz
2 GB RAM
Windows XP
I know its kinda running with coal, but actually, its just a phone emulator. What is your opinion?
I had the same problem. The emulator was slow as hell. You can significantly speed it up by changing the heap size allocated to it in AVD manager. Go to AVD Manager -> Select your device -> Click on "Details" button. The heap size will most probably be 24 or 48 (vm.heapSize: 24). Here's how you increase the heap size.
AVD Manager -> Select device -> Edit -> Hardware section (same window) -> Select "Max VM application heapsize" property -> Double click and edit the value to 512 or higher.
Restart the emulator (if already running).
It is just a very slow emulator. The best option is definately to test on a real phone.
I am using Intel Core2 Quad # 2.33HZ, 2.33Hz with 3GB of RAM. It take about 20 seconds to upload the app after making changes. You must upgrade your PC in order to test your apps on emulator. If you have android device, then good. Your PC will work fine.
Like cjk says, the emulator is incredibly slow. It fully emulates the core ARM architecture and can only be single threaded. Best you can do to help it is assign it to a lesser used core and increase the priority/niceness of the process.
I had the same type of specs on my computer while developing, indeed the emulator is too slow to work with. What is your screen resolution? In my case connecting to a monitor sped up the emulator, really lame..
My LCD's current screen resolution is 1600 * 900 and I am using Windows 7. Its working fine.
I have a macbook air (not very powerfull), the emulator was too slow. It was because the in the Emulation Options Use Host GPU was ticked. This might also help. its fine with:
Device: 3.2" QVGA
target: level 8
Memory Ram: 512
Heap: 128
Emulation options: not ticked.
hope it helps